Skip to main content

Go Live

Joint user acceptance testing is required for any vendor wanting to move from test to live environment. Paynow is obliged to conform to specific requirements from billers and to ensure vendors do the same.

note

The vendor must share their screen whilst these tests are carried out.

UAT Tests​

  1. Ensure the vendor can check and display their vendor wallet balance in their backend
  2. Ensure that customer information (at least MemberName and MemberAddress if present) is displayed on screen after payment AUTH
  3. Ensure the vendor's status inquiry interval for BeingProcessed payments adheres to specification. The Test Biller with member numbers starting with PP will be used during this test.
  4. Ensure that all entries in ReceiptHtml (if present) are shared with the customer. If displayed on screen, the customer must be able to download/print each individual entry — not combined into one.
  5. Ensure that all SMS in ReceiptSmses (if present) are sent to the customer's mobile phone. Each SMS must be sent individually, not combined.
  6. Ensure that the vendor responds to biller configuration webhook requests with:
    • 200 OK response
    • An inquiry to /api/payment/ListBillers?billerCodes=ABC,DEF,GHI (not /api/payment/ListBillers without filters)
  7. Ensure the vendor is not frequently calling /api/payment/ListBillers (only as needed after webhook from BillPay) and that biller configurations are stored in the local application database.

Helpful Notes​

tip

The following checklist is not part of UAT, but will help improve the operational and user experience of your end product.

  • Track your vendor wallet balance after each successful transaction (included in the response) and notify operational staff when the wallet falls below a predetermined amount. Take care not to flood staff with emails.
  • For transactions that remain in BeingProcessed for a prolonged period, assign a specific number of retries before flagging for manual intervention:
    • Notify operational staff
    • Notify the customer that you're attending the issue
    • Suspend status inquiries temporarily to decrease load
  • Have methods in place to promptly refund your customer if a transaction fails and cannot be retried
  • Implement the Auto Push Biller Configuration webhook to automatically reconfigure your product/price offering or notify staff of changes. If your system's pricing becomes out of sync with BillPay, API requests are likely to be rejected.