Central Bank of Libya SWIFT/BIC code

SWIFT/BIC code of Central Bank of Libya

CBLJLYLX and CBLJLYLXXXX are two spellings of the same SWIFT/BIC code, and both point to Central Bank of Libya in Tripoli. A SWIFT code shows the sending bank which institution is meant to get the money, a bit like a postal address for banks. In practice you usually come across it on international invoices, in payment forms and in the bank details that Central Bank of Libya provides.

Below we go through the practical questions: money coming in from abroad, paying someone in another country and how to verify a SWIFT code before you hit send. The BIC identifies a bank or branch, not a single account, which is why you always need the account number too.

How up to date is this code?

The details here are taken from publicly available data which we refresh regularly. Institutions merge, close branches and retire codes. The figures on this page are based on what is in our directory and not on information from Central Bank of Libya itself.

See the information here as a helpful check and rely on the recipient or Central Bank of Libya for the final confirmation. We are an independent comparison service for money transfers and not affiliated with Central Bank of Libya. Found an error? Tell us through the contact page so we can correct it.

Sending money abroad from Central Bank of Libya

A bank transfer abroad costs more than the fee suggests. Besides the transfer fee, correspondent or intermediary banks can deduct a fee, and when currencies are converted the bank often applies a rate below the real market rate.

Banks rarely show their exchange rate markup as a cost. A simple test: put the rate you get next to the mid-market rate for the same moment and work out the difference on your amount.

Specialist money transfer services frequently offer rates closer to the mid-market rate. On GoldexPay you can compare what recipients receive across providers, which makes the cheapest option easy to spot. Using a transfer service does not mean leaving Central Bank of Libya.

Why Central Bank of Libya has an 8- and an 11-character code

The structure of every SWIFT code never changes: four characters for the institution, two for the country and two for the location, plus an optional branch code. In this case, that core is CBLJLYLX.

XXX at the end of CBLJLYLXXXX does not stand for a placeholder or an error: it stands for the head office of Central Bank of Libya. Some forms insist on 11 characters, in which case you simply add XXX after CBLJLYLX.

Leave out spaces, dots when you enter CBLJLYLX. A wrong character can send a payment to another bank.

What to give a sender who pays you at Central Bank of Libya

For a transfer from abroad into your account at Central Bank of Libya, the sender needs not just the BIC. What they need is: the account holder’s name, account number or IBAN, CBLJLYLXXXX and in many cases your postal address.

Certain sending banks want the bank’s address in Tripoli; it does no harm to include it. Double-check every detail before you share them – a sender rarely spots a mistake in someone else’s details.

An incoming payment will not always arrive for the full amount. Charges on incoming payments vary from bank to bank. On invoices, you can agree how the fees are split.

How to check CBLJLYLX before you pay

The most reliable source for a SWIFT code is the bank details provided by the recipient – an invoice, a statement or a screenshot from online banking. Compare it with CBLJLYLX on this page; if they differ, ask before you pay.

If the code is wrong, the transfer might get stuck, bounce back or cost extra – sometimes after weeks of searching. Remember the account number: an error there can be more difficult to undo than a wrong BIC.

Many banking apps check the structure of an IBAN, but that does not prove the account belongs to the right person. More and more banks check the payee name against the account before you confirm; take any warning seriously. When you pay someone new, some people start with a small test amount before sending the rest.

Changed bank details? Be careful

Scammers often send fake invoices with changed bank details sent from what looks like a familiar address. A valid SWIFT code tells you nothing about who owns the account.

Never rely on contact details from the same email that contains the new account. Pressure or secrecy tend to be red flags – a real supplier can wait a day. Already paid? Contact your bank without delay and have them try to recall the payment; also report it to the police.

Fraud can also work the other way. Someone sends too much and wants you to refund the extra. A payment confirmation from the sender is no proof.

How long does an international transfer to Central Bank of Libya take?

How fast a transfer arrives at Central Bank of Libya is determined by several factors: which currency you send, the number of banks in between, cut-off times and time zones. Transfers sent after the cut-off time or on weekends and holidays often go out the next business day. Extra checks by one of the banks may also add a delay.

Many banks are connected to SWIFT gpi. Each gpi transfer carries a unique transaction reference, the UETR. Keep the payment confirmation until the money has arrived; it contains the details a bank needs to start a trace.

If the money does not arrive after a few business days, the person who paid should start with the bank that sent it. On the receiving end, it helps to check your account to see a partial amount.

Which of the 5 codes of Central Bank of Libya do you need?

We have 5 SWIFT/BIC codes for Central Bank of Libya. Next to the head office code CBLJLYLXXXX, you will find codes for branches, departments or specific services.

In most cases there is no need to pick a branch: payments addressed to CBLJLYLXXXX are routed within Central Bank of Libya correctly. Branch codes are only needed if the recipient’s bank specifically mentions it.

The safest approach is to copy the code straight from the recipient’s bank details. Branch codes are sometimes changed or retired when banks reorganise, so a code from an old document is not always valid.