A problem payment in a Bali transaction

What should happen first?

Preserve sending confirmation, date, amount, currency, recipient, payment reference, transfer ID, correspondence and status screen. Then review the contractual condition without sending a duplicate payment or changing account details from an unverified message.

The short answer

“Delayed”, “held” and “returned” are not the same status, and the reason should not be guessed. You need a written request to bank or provider, written notice to the contractual party and one incident record linked to the payment ledger.

Evidence scope

Checked on

2026-10-15

Established

• Rate information does not explain an individual transfer.

Not established

• Cause, timing or outcome of a problem transfer.

Do not pay twice to remove anxiety

A second transfer may create a new problem while the first remains unidentified. First collect transaction reference, status, sending confirmation and provider response. If the contractual date is close, notify the other party through the specified channel of the fact and that it is being checked.

Make an incident card

One factual page is better than a long chat: payment-ledger row, amount, currency, reference, time, status, agreement clause, contacts, requests sent and next expected document. Write separately what is known and what remains unconfirmed.

A rate benchmark does not explain the incident

Official rate information is useful context, but does not explain why a particular transfer is delayed or returned and does not predict outcome. Do not replace a provider response with reasoning about rates.

Decision steps

1. Step 1

   Do not send a duplicate before identifying the first transfer.

2. Step 2

   Save reference, status and every confirmation.

3. Step 3

   Send written request to provider and notice to contractual party.

4. Step 4

   Link incident to contractual date and payment ledger.

5. Step 5

   Act further only after confirmed status and agreement review.

What to check

Sources

Next reading