Process a PayID Transaction

This article describes the different scenarios that can be simulated in the Sandbox environment for PayID transactions. The payment.amount field in POST /paymentrequests is used to control the desired behaviour.

NOTE: PayID transactions are created asynchronously as part of the Payment Request flow. Use the trigger amounts below when creating a Payment Request to simulate different outcomes.

Any payment.amount value other than 10110 or 10120 will result in a paymentRequestStatus of created — no payment is made and no transaction is generated.

Simulate a Payment Request with no payment

This scenario simulates a Payment Request being created but no payment is made by the customer. The paymentRequestStatus will be set to created and remain there — no PayID transaction is generated.

Payload Property	Value
payment.amount	10110

Simulate a Payment Request with a successful payment

This scenario simulates a Payment Request being created followed by a successful payment from the customer through their banking app. The paymentRequestStatus will transition from created to completed. You will receive two payment_requests webhook notifications (one per status change) and, if subscribed to the transactions event, an additional transaction webhook.

Payload Property	Value
payment.amount	10120