BRI UETR Tracking.
Check what the trackers can show.
When a BRI transfer is delayed, "sent" is not a real answer. uetr.ai checks public bank trackers and organizes available status context before your next bank conversation.
Track BRI transfer
See what the banks have reported about your transfer, and get alerted when the payment reaches a further stage.
BRI SWIFT code, IBAN, and international wire transfer details
The SWIFT/BIC code, IBAN format, and routing details for PT Bank Rakyat Indonesia (Persero) Tbk (Indonesia (ID)). Check each one against your own payment advice before you send money.
PT Bank Rakyat Indonesia (Persero) Tbk
BRI I Building, Jl. Jenderal Sudirman Kav. 44-46, Jakarta 10210, Indonesia
Not used. Indonesia does not use IBANs: an overseas sender uses the SWIFT/BIC code BRINIDJA with the BRI account number and the account name exactly as BRI holds it. Inside Indonesia, a transfer from another bank uses BRI's domestic bank code in front of the account number; take that code from BRI's own instructions.
How this BIC breaks down
BRI international wires, BIC codes, and UETR tracking
BRI, BRINIDJA, and what an overseas sender needs
BRINIDJA (BRINIDJAXXX in full) is the SWIFT/BIC code BRI publishes on its own BRIfast Remittance page. It belongs to PT Bank Rakyat Indonesia (Persero) Tbk in Jakarta. BRI publishes that single code. If the instructions BRI gave the recipient show a different or longer code, use the one on those instructions and confirm it on your payment advice. Indonesia does not use IBANs. The sender needs the BIC, the BRI account number and the account name exactly as BRI holds it. Inside Indonesia, transfers from another bank use BRI's domestic bank code in front of the account number. Those domestic transfers never carry a UETR.
The UETR belongs to the SWIFT leg. A payment that reaches or leaves BRI over the SWIFT network carries the 36-character reference from the first bank to the last. That is what lets you see which bank last reported it.
Is there a BRI SWIFT tracker?
Yes. BRI runs the BRIFAST Tracker, a public page that loads without a login. It asks for a single transaction ID to start the search. For a SWIFT payment that identifier is the UETR. When BRI has recorded the payment, the page reports a Latest Status (Complete, In Process or Rejected), the instructed amount and currency, and the value date. It also shows a Deducts field, the time of the latest update, and a tracking detail table of the movements BRI has recorded between the banks involved. The Deducts field carries the charge-bearing code, for example DEBT, meaning the sender bears the charges. It is not an amount.
What the page reports is BRI's view of the payment. A cross-border transfer usually passes through correspondent banks that BRI does not act for. Several of them publish trackers of their own. uetr.ai checks the public bank trackers it can reach for the same UETR, so the reports those sources show against it appear on one page. A source that shows only its latest snapshot contributes that snapshot, not every earlier report. A reporting bank is a source that filed a report, not a position on the payment's route. BRI remains the official source for whether the account was credited.
SWIFT transfer or BRIFAST remittance? Identify the route first
BRIFAST is also the name of BRI's remittance service. It brings money into Indonesia through partner remittance companies as well as over SWIFT. A reference issued by a remittance partner or a money transfer app belongs to that partner's system. It is not a UETR. It will not return anything on a SWIFT tracker, and the payment may never have travelled over SWIFT at all. BRI's BRIfast Remittance site has its own Track Your Transaction page for those references.
So settle the route before you paste anything. If the sender's bank issued a SWIFT payment confirmation, an MT103-format advice or a pacs.008-format document, the reference on it is a UETR. Then the BRIFAST Tracker and uetr.ai both apply. If the sender used a remittance partner, ask the partner for the status first. Ask whether the last leg to BRI went over SWIFT.
Tracking a BRI SWIFT transfer with the UETR
On an MT103-format advice it is field 121. On a pacs.008-format document it is the UETR element inside PmtId. A sender who paid from a corporate account can read it from the transaction record in the bank's business channel. A retail sender asks the sending bank for the SWIFT copy of the payment. The recipient can ask the sender for it, because the same 36-character reference works from either side.
Paste the UETR into uetr.ai. We check the public SWIFT gpi tracker sources we can reach, then explain the status in plain English, for example ACSP for accepted and in process, or ACCC for credited. The free check re-checks the same reference on its own afterwards. You do not have to keep returning to a tracker page and pasting the reference again.
When the BRIFAST Tracker finds nothing
A transaction-not-found result means BRI has no record under that identifier. That happens for three reasons: the payment has not reached BRI yet, BRI never handled it, or the reference is not the UETR (a remittance partner's code or the sending bank's own short reference will not match). It is not evidence that the payment was never sent. It is not a rejection either. A rejection shows as a Rejected status on the tracker, or as RJCT on the SWIFT network. It is a report about the payment instruction, not a return of the money.
When the tracker is quiet, check the same UETR on uetr.ai to see whether any bank has reported at all. The free check shows the plain-language status and the bank count. The paid trail names each reporting bank. Give the payment its normal delivery time. Then, if no tracker has shown a credit, a newer step, or a final report such as RJCT, ask the sending bank to open a trace with the reference. A payment that has not reached BRI yet is a reason to wait, not to pay for a trace. A tracker report does not prove that the payment reached BRI. Only BRI can confirm receipt. If the sending bank's confirmation says the payment left and the account shows nothing, give BRI the UETR, the exact amount and currency as sent, and the value date. Then staff can search incoming and unapplied payments.
See an example UETR trace across correspondent banks
A made-up payment, hop by hop, so you can see the shape of a real trace before you run one. Nothing here touches SWIFT, a bank, or any live payment record.
Why a BRI transfer can still go silent with no update
When you start an international bank transfer through BRI, the transfer travels across the SWIFT network. Instead of going directly, your transfer routes step by step through intermediate institutions known as correspondent banks.
If a delay occurs, checking the status in your BRImo or QLola by BRI may show only the information available to BRI. Other events may depend on correspondent banks, network confirmations, and the access rights of the banks involved.
uetr.ai acts as an independent information monitor. When you provide your 36-character UETR (Unique End-to-end Transaction Reference), we check public bank trackers that can be queried with the details you provide.
We assemble available events into a single plain-English timeline. Use that context to ask more precise questions of the sending or receiving bank.
Why another view can help
One bank's view may not show the full payment path. uetr.ai checks multiple public bank trackers for the same UETR and brings the available reports into one view. The free check tells you how many banks have reported. The paid view names the reporting banks and shows their exact status codes.
A BIC directory is not a payment tracker
Most sites that come up for "BRI SWIFT code" list the bank's registration details and stop there. That tells you where to send money, not where yours is.
| Feature | uetr.ai | A BIC lookup directory |
|---|---|---|
| The BIC itself | Listed, with one-click copy and a breakdown of every segment. | Listed. |
| Looking up a payment by UETR | Yes, wherever a public tracker reports it | No. It holds branch registrations, not payments. |
| What the banks in the middle reported | ACSP, ACWC, and RJCT, explained in plain English where they are visible. | Nothing. A register carries no payment events. |
| Worked examples | A sample trace and a BIC breakdown you can run on this page. | A table of codes. |
| Getting to it | Loads without an account, and prints or pastes into a ticket as it is. | Also open, but it stops at the registration record. |
Break down a SWIFT/BIC code
Paste any BIC to see which part is the bank, the country, the city, and the branch. Confirm the routing details with the bank itself before you send money on the strength of them.
How an international wire transfer actually travels
How SWIFT routing and correspondent banking move a BRI wire, and why the UETR is the one thing that follows it the whole distance.
01/ Correspondent banks
Two banks can only pay each other directly if one holds an account with the other. Where BRI has no such account with the receiving bank, it hands the payment to a correspondent bank that holds accounts with both sides, and sometimes to a second one after that.
Those accounts are the Nostro and Vostro ledgers. Every bank on that route gets to inspect the payment, screen it, take a fee, and work to its own cut-off times. Each one is somewhere your money can sit.
02/ UETR tracking in MT103 and pacs.008
Before SWIFT gpi, a payment that left BRI left your view with it. The UETR changed that: one 36-character reference that the banks handling the payment report against. On an MT103-format advice it is field 121. On a pacs.008-format document it is the UETR element inside PmtId.
It is five hyphenated groups, and it stays identical from BRI to the beneficiary bank. That is the whole point of it. Give uetr.ai that reference and we go and read what the public trackers hold against it.
03/ What each SWIFT gpi status code means
ACSP means the payment has been accepted and is moving through the correspondent chain. It has not been credited to the beneficiary yet.
ACWC means a bank accepted the payment but changed something on it. Ask which bank changed what, and whether it affects the amount, the routing, or the fees.
RJCT means a bank in the chain refused the payment instruction. Ask the sending bank for the reason code and what happens to the funds.
ACCC means the beneficiary bank has credited the money to the beneficiary's account. The transfer is complete.
04/ Why a wire transfer gets delayed
Sanctions and compliance screening
Every bank on the route screens the names on the payment. A near-match to a listed name is enough to pull it out for a person to review.
Cut-off times and holidays
Miss a bank's daily cut-off and the payment waits for tomorrow. A public holiday anywhere on the route does the same thing.
Intermediary bank fees
Under SHA or BEN charges, each intermediary bank on the route can take its cut before passing the money on, so less arrives than you sent.
Where is your BRI wire stuck?
A BRI payment can pause at any hop in the correspondent chain. The same UETR travels with it the whole way, so tracking it shows which institution reported last and what that bank reported.
How to find your UETR on a BRI transfer
A UETR (Unique End-to-end Transaction Reference) is a standard 36-character reference commonly used for SWIFT gpi payment tracking.
Get the SWIFT confirmation
Ask the sending bank for the SWIFT copy of the payment, the confirmation it issued when the transfer was released. A sender who paid from a business channel opens the transaction record of that payment; a BRI customer who sent the payment opens it in QLola by BRI or asks a branch.
Locate the UETR
Copy the 36-character UETR from the document. On an MT103-format advice it is field 121. On a pacs.008-format document it is the UETR element inside PmtId. A remittance partner's reference is not a UETR and will not track on a SWIFT tracker.
Check more than one bank
Paste the UETR in the form above. uetr.ai checks multiple international banks on the SWIFT network for that same reference, not only BRI. It is free and needs no account, and we keep re-checking every 24 hours for up to 30 days from submission while the transfer is still in progress, emailing you when the payment reaches a further stage.
Typically located on the SWIFT payment confirmation or transaction record from the sending bank. If not visible in your online dashboard, ask BRI's customer support for the bank-issued payment confirmation or the UETR itself.
BRI wire status codes in plain English
When you track a BRI UETR, the SWIFT gpi network reports a status code. Here is what each one means for your money and what to do next. These codes follow the ISO 20022 External Code Sets and are the same across every bank.
| Status | What it means for your money | What to do |
|---|---|---|
| ACSPAccepted settlement in process | In transit. A bank accepted the payment and it is moving through the chain. | Keep tracking the UETR for the next reported step. |
| ACSCAccepted settlement completed | Settlement between the banks is complete on the sending side. | Check that the beneficiary bank has credited the account. |
| ACCCAccepted credit settlement completed | Credited to the beneficiary's account. The money has arrived. | Confirm receipt with the recipient. |
| ACWCAccepted with change | Accepted, but a detail was changed (for example a charge or a corrected account). | Ask the bank what changed and whether it affects the amount received. |
| PDNGPending | Held while a bank runs a check or waits for more information. | Ask which bank is holding it and why, often a compliance review. |
| RJCTRejected | A bank rejected the payment or instruction. | Ask the sending bank for the rejection reason and next steps. |
Track a SWIFT transfer at another bank
The same UETR tracking guide and SWIFT/BIC details for every other bank we cover.
FAQ
BRI wire tracking questions
What is BRI's SWIFT code?
BRINIDJA (BRINIDJAXXX in full) is the SWIFT/BIC code BRI publishes on its own BRIfast Remittance page. It belongs to PT Bank Rakyat Indonesia (Persero) Tbk in Jakarta. If the instructions BRI gave the recipient show a different code, use that one and confirm it on your payment advice.
Does BRI have an IBAN?
No. Indonesia does not use IBANs. An overseas sender uses the SWIFT/BIC code BRINIDJA with the BRI account number and the account name exactly as BRI holds it. Inside Indonesia, a transfer from another bank uses BRI's domestic bank code in front of the account number; take that code from BRI's own instructions.
What is the BRIFAST Tracker?
The BRIFAST Tracker is BRI's public SWIFT payment tracker. It loads without a login and asks for a transaction ID. For a SWIFT payment that is the UETR. It reports BRI's latest status for the payment (Complete, In Process or Rejected), the instructed amount and the value date. It also shows a Deducts field and the movements BRI recorded between the banks involved. The Deducts field carries the charge-bearing code, DEBT for example, not a fee amount.
Is a BRIFAST remittance the same as a SWIFT transfer?
Not always. BRIFAST Remittance brings money into Indonesia through partner remittance companies as well as over SWIFT. A reference from a remittance partner is not a UETR, and it does not work on a SWIFT tracker. BRI's BRIfast Remittance site has a separate Track Your Transaction page for those. Only a payment sent over the SWIFT network carries a UETR.
How do I track a SWIFT transfer to BRI?
Get the UETR from the sending bank's SWIFT confirmation. On an MT103-format advice it is field 121. On a pacs.008-format document it is the UETR element inside PmtId. Enter it on the BRIFAST Tracker for BRI's view, and paste it into uetr.ai to see what other public bank trackers have reported against the same reference.
What does In Process mean on the BRIFAST Tracker?
In Process is the label BRI uses for a payment it had recorded but not yet completed when it filed that report. At that time the transfer was still moving, and BRI had not recorded a credit. It describes what BRI knew when it reported, not the payment now. So read it with the report date. A later leg may not be shown by any tracker you can reach. Complete means BRI recorded the payment as finished. Rejected means the instruction was refused. That is a report about the instruction, not a return of the money.
Why does the BRIFAST Tracker say transaction not found?
BRI has no record under that identifier. The payment may not have reached BRI yet. BRI may not be on its route. Or the reference you entered is not the UETR (a remittance partner's code or a sending bank's short reference will not match). It is not evidence that the payment was never sent. Check the UETR on uetr.ai. Give the payment its normal delivery time. Then, if no tracker has shown a credit, a newer step, or a final report such as RJCT, ask the sending bank to trace it. A payment that has not reached BRI yet is a reason to wait, not to pay for a trace.
Where do I find the UETR for a BRI transfer?
On the SWIFT payment confirmation from the sending bank. On an MT103-format advice it is field 121. On a pacs.008-format document it is the UETR element inside PmtId. A BRI customer who sent the payment can open the transaction record in QLola by BRI or ask a branch for the SWIFT copy.
How long does a SWIFT transfer to BRI take?
There is no single figure. It depends on the corridor, on the correspondent banks on the route, and on cut-off times, weekends and public holidays in either country. The UETR shows the latest reported status and how many banks have reported. On the paid trail it also shows which bank reported last and when. Your bank can quote that when it raises an enquiry.
Does uetr.ai keep checking my BRI transfer, or is it a one-time lookup?
It keeps checking. A free check is not a single lookup: while the transfer is still in progress, uetr.ai re-checks the same UETR once every 24 hours for up to 30 days from submission and emails you when the payment reaches a further stage, so you do not have to keep opening a tracker page and pasting the reference again. A bank tracker page reports the status at the moment you open it. Paid plans re-check every few minutes instead of once a day.
Can I see what banks other than BRI reported on the payment?
Yes. One bank's view may not show the full payment path. uetr.ai queries multiple international banks on the SWIFT network for the same UETR and consolidates what each one reports into a single timeline. The free check tells you how many banks have reported against your UETR. The bank-by-bank trail of reporting sources, ordered by the stage each report describes and with the exact code each returned, is part of the paid plan; the order of reports is not the payment's route, since a public tracker can report a payment its bank did not handle.
What reference SWIFT/BIC code is listed for BRI?
This guide lists BRINIDJAXXX as a reference SWIFT code for BRI, with base BIC BRINIDJA. Confirm the correct BIC, branch, and routing instructions directly with BRI before sending or acting on a payment.
How do I check a BRI wire transfer with a UETR?
To check a BRI international wire transfer, locate the 36-character UETR (Unique End-to-end Transaction Reference) on the payment advice. On an MT103-format advice it is field 121. On a pacs.008-format document it is the UETR element inside PmtId. Enter this UETR on uetr.ai to check public bank trackers for available status information. Your bank remains the official source for settlement and routing confirmation.
Can uetr.ai trace domestic wires for BRI?
No, uetr.ai is designed for international wires carrying a SWIFT UETR. Domestic wires (like Fedwire, ACH, or SEPA payments without UETR headers) use domestic clearing references and are outside this lookup unless a tracker source can be checked with the details you provide.
Is my data secure when checking BRI UETRs?
Yes. The service is designed for read-only lookups. We never request passwords, tokens, or personal bank login info. We use the payment reference, amount, currency, and date to query bank trackers and operate the monitoring service.