Skip to main content
This guide covers inbound payments - the ones you receive. Every inbound SWIFT credit transfer must be confirmed back to the SWIFT network under the Universal Confirmations policy. In automatic mode (the default) the platform does this for you with no operator involvement: the payment is credited on receipt and the final confirmation goes to the SWIFT gpi Tracker immediately.
For outbound payments (the ones you send), see Payment statuses.
Universal Confirmations compliance is not just a formality: it is a prerequisite for tracking your outbound payments via the SWIFT Frontend API. The platform guarantees that compliance for you - a confirmation is always sent on time, in this mode and in manual mode.
The platform builds, signs and submits the confirmation messages on your behalf. No integration work is required - the mode is a single tenant setting.

​
Confirmation modes at a glance

​
How automatic confirmation works

1

Payment received and credited

The inbound payment lands directly as Completed - the beneficiary is credited on receipt, with no intermediate status. You receive a single webhook (Completed, direction=INBOUND).
2

Final confirmation sent

ACCC - “payment credited to beneficiary” - is sent to the gpi Tracker immediately. The sender’s bank sees the outcome in real time.

​
Cover payments (COVE)

Some correspondents settle in two parts: the customer payment only announces the transfer, while the actual money moves separately as a bank-to-bank cover transfer. The payment must not be credited until the cover arrives.
1

Payment announced, funds not yet in

The inbound payment lands as Accepted and waits with the reason awaiting_cover (visible via GET /v3/payments/{id}, not in the webhook). The beneficiary is not credited yet. An interim ACSP/G004 confirmation (“awaiting cover”) is sent to the Tracker immediately.
2

Cover arrives

The matching cover transfer comes in and the platform matches it to the waiting payment automatically.
3

Auto-completed

In automatic mode the payment completes right away: status Completed, webhook sent, final ACCC confirmation goes to the Tracker.

​
Confirmation status codes

​
Returning a completed payment

Even after a payment is completed and credited, you can still return it to the sender - a beneficiary’s request, a compliance issue that surfaced later. The original stays Completed; the money goes back as a separate Payment return transaction.

Payment returns

Full flow, return reasons and the returns API

​
Webhooks

​
API Reference

Get payment

GET /v3/payments/{id} - read the statusReason (awaiting_cover)

Return payment

POST /v3/payments/{id}/returns - return a completed payment

​
Next Steps

Manual confirmation

Hold payments for compliance review instead

Statements

Reconcile received funds
Last modified on September 4, 2026