Use Cases

Bill Payment Use Case

Below is how the typical use of the Scan to Pay system works from the merchant/PSP perspective for a Bill Payment.

  1. Merchant/PSP needs a payment to be done. Merchant/PSP calls the Create Code API to generate a code that represents the transaction. This code is a use once code so it will not work once the payment is made.
  2. Merchant/PSP gives the code to the Cardholder. The Merchant/PSP prints this code as a QR allowing the cardholder to use it.
  3. Merchant/PSP waits. The merchant/PSP is waiting for the cardholder to make the purchase.
  4. Cardholder makes payment. The cardholder will scan a QR or manually enter it, follow the prompts and make the payment.
  5. Scan to Pay will notify the merchant/PSP. Once the transaction has come to an end, either successfully or not, Scan to Pay will notify the merchant. We support 3 methods: HTTP, EMAIL and SMS.
  6. Realtime Notification. If HTTP is the method of notification, Scan to Pay will perform an HTTP request to the merchant/PSP designated URL. The merchant needs to verify all the details and return an HTTP success of 200. If for whatever reason the merchant decides to return a non-200, Scan to Pay will reverse the transaction.

If the merchant/PSP does not wish to recreate a code each time, the merchant may reuse the same code by calling the Update Code Amount API call with the new amount. This will reactivate the code with the new amount and allow the cardholder to make the payment.

Static Code Use Case

Below is how the typical use of the Scan to Pay system works from the merchant/PSP perspective.

The following needs to be done only once per device:

  1. Merchant/PSP needs to enable a device to accept card payments. Merchant/PSP calls the Create Code API to generate a code that represents the transaction. This code will represent this device.
  2. Merchant/PSP displays the code. The Merchant/PSP can place a sticker on the device of this QR code allowing a cardholder to use it.

The following is done for each transaction:

  1. Merchant/PSP needs a payment. The merchant/PSP makes the Update Code Amount API call. This will tie the amount to the QR code that is presented to the cardholder.
  2. Merchant/PSP waits. The merchant/PSP is waiting for the cardholder to make the purchase.
  3. Cardholder makes payment. The cardholder will scan a QR or manually enter it, follow the prompts, and make the payment.
  4. Scan to Pay will notify the merchant/PSP. Once the transaction has come to an end, either successfully or not, Scan to Pay will notify the merchant. We support 3 methods: HTTP, EMAIL, and SMS.
  5. Realtime Notification. If HTTP is the method of notification, Scan to Pay will perform an HTTP request to the merchant/PSP designated URL. The merchant needs to verify all the details and return an HTTP success of 200. If for whatever reason the merchant decides to return a non-200, Scan to Pay will reverse the transaction.