Overview

Let your customers pay straight from their anb accounts: simply, securely and with full control.

Open banking PIS enables you, as a licensed Payment Initiation Service Provider (PISP), to initiate domestic payments in SAR directly from your customers' anb accounts, with their explicit consent and in alignment with all regulatory requirements in KSA. Customers approve every payment in anb's secure journey, using the same login they already trust, so they stay in control at every step.

Offer a seamless pay-by-account experience in your app or website, whether your customers want to pay now or later:

  • Single Instant Payment (SIP), pay now: the payment is executed immediately once the customer approves it.

  • Single Future Dated Payment (SFDP), pay later: the customer schedules a one-off payment for a future date, and it is executed on that date with no need to approve it again.

 

API Flows

1. Payment Consent Request

The flow will begin with a PSU who provides consent for a TPP to initiate a payment from their anb account.

 

2. Setup Payment Consent

The TPP will request the payment consent from ANB. To support this, the TPP will:

  • Successfully authenticate with ANB authorization server to obtain an access token.

  • Use the access token to create a payment consent request against ANB resource server.

This step should be fulfilled by a POST request to the /payment-consents resource made available on ANB resource server. ANB will acknowledge the request and return a ConsentId.

The payment consent request will include the payment details, such as the amount in SAR, payee details and purpose of payment, and for SFDP the requested execution date.

3. Authorize Payment Consent

The TPP will redirect the PSU to ANB to authenticate and authorize the consent. The PSU reviews the payment details, including fees and VAT, and selects the payment account if the TPP did not provide one. 

 

4. Payment Initiation

  • SIP: Once the PSU authorizes the consent, ANB creates the payment and executes it immediately. The TPP must not send a separate POST request to /payments; the PaymentId is linked to the consent.

  • SFDP: On the requested execution date, the TPP sends a POST request to the /payments resource using the authorized ConsentId. ANB validates the request against the consent, executes the payment and returns a PaymentId.

 

5. Payment Status

The TPP can retrieve the consent status using GET /payment-consents/{ConsentId} and the payment status using GET /payments/{PaymentId}.