Payments

  • Updated on Feb 28, 2025
  • Published on Feb 26, 2025
  • 3 minute(s) read
Prev Next

Payments is the core of our value proposition, with Payments API being key for your operating model

Actions available via PagoNxt Payments API:

  • Instruct a payment via pacs.008 or pacs.009 endpoints, according to type of payment

  • Retrieve a payment status, by providing Payment ID

Current payments scope include payouts in 20+ currencies to 140+ markets!

High level outbound payment flow

Highlights on outbound payment flow:

  • Unique Field must be “InstrID” and will be used for tracking and will be the debit reference

  • Duplicate checks are performed on the “InstrId”

  • Like-for-like payments and FX payments available

    • Like-for-like payments are payments without FX → Settlement account CCY = Payment CCY

    • Payments with embedded FX → Settlement account CCY differs from Payment CCY, and payment flow includes FX transaction. No additional developments needed for this

  • After submission of the payment from PagoNxt Client, a synchronous response of PDNG in the pacs.002 webhook

  • Formatting guidelines for specific currencies available under request

  • PagoNxt conducts Wire Transfer checks and payment screening on all payments before instructing the outbound payment

  • Payment tracking via webhook (pacs.002) and API available (GET/payments_iso/pacs002/v10/{payment_id})

Payment statuses available via Webhook:

Code

Description

PNDG

Payment pending

ACSP

Payment accepted and settlement pending

ACSC

Payment accepted and settlement completed

ACCC

Beneficiary account credited

RJCT

Payment rejected

  • ACCC and RJCT are final statuses

  • ACCC informed based on availability (dependency on scheme GPI compliance & beneficiary bank updates)

Rejections & Returns

  • Rejections will be informed via webhook or API available (GET/payments_iso/pacs002/v10/{payment_id}), where pacs.002 will include rejection reason code

  • Returns will be sent to PagoNxt client in pacs.004 format and will be visible as a credit on the client account which can be seen via

    • Webhook → credit webhook with camt.054 embedded object

    • MT statements → MT910, MT940 & MT42

    • Client Portal (online platform)

Details of rejection and return codes below:

  • AC01​ → Format of the account number specified is not correct

  • AC02​ → Format of the account number specified is non-numeric

  • AC03​ → Format of the account number specified is not valid for local sort/national clearing code

  • AC04​ → Account number specified has been closed on the receiver's books

  • AC05​ → Account number specified is not a valid account at the Account With Institution

  • AC06​ → Account specified is blocked, prohibiting posting of transactions against it

  • AM01​ → Specified transaction/message amount is equal to zero.

  • AM02​ → Specified transaction/message amount is greater than allowed maximum

  • AM03​ → Specified transaction/message amount is in a non-processable currency outside of existing agreement

  • AM04​ → Amount of funds available to cover specified transaction/message amount is insufficient

  • AM05​ → This transaction/message appears to have been duplicated

  • AM06​ → Specified transaction amount is less than agreed minimum

  • AM07​ → Amount specified in transaction/message has been blocked by regulatory authorities

  • AM08​ → Specified charges amount is not as agreed between sender and receiver

  • BE01​ → Specification of beneficiary is not consistent with associated account number

  • BE02​ → Beneficiary specified is not known at associated sort/national clearing code

  • AG08 → Invalid access right (currency not allow)

  • FF06 → Category Purpose code is missing or invalid

  • BE03​ → Beneficiary specified no longer exists in the books

  • BE04​ → Specification of beneficiary address, which is required for payment, is missing/not correct

  • BE05​ → Party who initiated the transaction/message is not recognised by the beneficiary

  • AG01​ → No agreement is on file at the receiver for affecting associated transaction/message

  • AG02​ → Bank Operation code specified in the transaction/message is not valid for receiver

  • DT01​ → Invalid date (for example, wrong settlement date)

  • MS01​ → Reason has not been specified due to sensitivities

  • PY01​ → Unknown Account-With Institution

  • RF01​ → Transaction reference is not unique within the message

  • ED01​ → Correspondent bank not possible

  • RC02​ → Routing code specified in the transaction/message is not numeric

  • RC03​ → Routing code specified in the transaction/message is not valid for local clearing

  • RC04​ → Routing code specified in the transaction/message refers to a closed branch

  • RR01​ → Specification of the ordering customer's account or unique identification needed for reasons of regulatory requirements is insufficient or missing

  • RR02​ → Specification of the ordering customer's name and/or address needed for regulatory requirements is insufficient or missing

  • RR03​ → Specification of the beneficiary customer's name and/or address needed for regulatory requirements is insufficient or missing

  • RR06 → Tax information missing, incomplete or invalid

  • NARR → Narrative reason