Skip to content

Go-live checklist

Work through this before you point an application at production.

  • Your Pesepay merchant account has been approved (see Onboarding)
  • You’ve swapped sandbox base URLs (api.test.sandbox.pesepay.com) for production (api.pesepay.com), or turned off your server library’s sandbox switch — see API Introduction
  • Your production integration key and encryption key are stored as server-side secrets, never in client code — see API keys & credentials
  • Sandbox keys are gone from the production build entirely, not just unused
  • Your payout account is configured and approved, for every currency you charge in
  • resultUrl is a publicly reachable HTTPS endpoint on your server that handles the result callback
  • Your handler verifies before fulfilling — it calls Check Payment Status rather than trusting the callback body (why)
  • Your handler is idempotent, keyed on referenceNumber
  • You run a reconciliation job for orders whose callback never arrived — callbacks are never retried
  • Nothing marks an order paid on returnUrl alone
  • You’ve made a small-value production payment with every method you plan to offer. The sandbox can’t exercise InnBucks, O’mari, Zimswitch, PayGo or any ZiG checkout, and it runs neither 3-D Secure nor the card providers’ forms
  • You’ve tested a failed payment per method, not just successes
  • Your checkout validates amounts against each method’s limits — they differ per method and currency, and Get Payment Methods by Currency returns the live values
  • If you accept EcoCash, you handle payments above $500 — the customer sees several prompts, and a partial failure reverses the whole payment
  • Your error handling covers the statuses in the error catalogue and the non-success transaction statuses, not just the happy path
  • Your page creates one transaction per order and renders the stored reference on every visit
  • The transaction’s returnUrl points at your checkout page, so a customer back from 3-D Secure sees the result there
  • Your Content-Security-Policy allows the Pesepay origins and the customer’s bank
  • Your server fulfils from the result callback and a status check, not from the element’s finished event