Absa Pay Integration Process
No integration changes are required to include Absa Pay.
Additional optional payment request fields
The following optional fields can be passed in for the Absa Pay flow:
| Request Field | Description | Type |
|---|---|---|
| payerDisplayNarrative | This is the description of the goods or services that the user is purchasing. This is defaulted to {payee_name} payment. | String |
| merchantDetails.name | This is used to customise the payee name field which is shown on the approval prompt in the Absa application. This is defaulted to the configured client name. | String |
Within the payment request mutation, this looks as follows:
Testing Absa Pay Scenarios
Our sandbox environment allows simulation of specific Absa Pay scenarios that users may experience in production, including how a user could handle MFA (multi-factor authentication) in their Absa app. To simulate these cases, the beneficiaryReference of your payment request can be tweaked as follows:
| Scenario | Beneficiary Reference |
|---|---|
| MFA successful and payment completed for user with single account | success |
| MFA successful and payment completed for user with multiple accounts | success-multiple |
| MFA request timed out | success-timeout |
| MFA request declined by user | success-declined |
| Insufficient funds | success-insufficient |
| Daily limit exceeded | success-dailyLimit |
| MFA successful, but payment fails | success-paymentFail |
| Payment initiation failure at Absa | failed |
| Payment intiated from an account without an Absa application | notADigitalCustomer |
| Payment intiated from non-existent Absa account | noAccountFound |
| Payment intiated for a beneficiary that has already been paid | paidBeneficiary |
| Payment intiated from a business account that cannot initiate Absa Pay payments | invalidBusinessAcc |
| Duplicate payment intiated | duplicatePayment |