Business Rules
General Rules
- On the Scan to Pay API a PSP or Merchant accessing the API must be able to process a Reversal, or a full or partial Refund. The PSP or Merchant accessing the API to process either a Reversal or Request must be authenticated using the API user name and password obtained from the Scan to Pay Portal.
- API Reversals and Refunds can be viewed as a transaction on the Portal.
- The timeframe for when a Refund or Reversal can be processed will be determined by the issuing bank. Scan to Pay will allow the transaction to be processed but it is up to the issuing bank to reject the transaction.
- A Reversal for an already refunded transaction, partial or full, is not allowed.
- A full or partial Refund for an already reversed transaction is not allowed.
- A Refund or Reversal can be processed regardless of the card from the original transaction being linked to the transacting MSISDN/mobile number at the time the Refund or Reversal is processed.
- If a Refund or a Reversal with incorrect API credentials is attempted this will result in a security violation.
- If a Refund is attempted against a debit card this will result in an invalid card error.
Reversal Specific Rules
- Reversals must only be processed on the full amount and no partial reversal must be allowed. No amount input field is required as the reversal amount cannot be changed and is as per the original purchase amount.
- Only one successful reversal per transaction Id must be allowed.
- Reversals can be done on all card types.
- If a reversal is processed outside of the permitted timeframe an ISO response is returned from the bank.
Refund Specific Rules
- Refunds can be processed on the full amount or partially.
- Refunds can only be processed on Credit and Cheque cards.
- A partial refund must be allowed on a transaction Id for a successful transaction.
Updated about 2 years ago