Getting started

Prerequisites

Four things before you write any code. If you have all of them already, skip straight to Authentication.

  1. An active QRPay merchant account. Payments are created against a merchant account — register if you don’t have one, or log in to the one you have.
  2. API keys from your merchant panel. Open Developer settings in the merchant dashboard and collect your Client/Primary key and Secret key. New keys start in SANDBOX mode, so you can build and test without moving real money.
  3. A server reachable over HTTPS. QRPay redirects your customer back to the return_url (and optional cancel_url) you supply, and your Secret key must only ever be used server-side — so you need a publicly reachable HTTPS endpoint to receive the redirect and to make the API calls from.
  4. Any HTTP client. The API is plain JSON over REST. The examples in these docs use PHP with Guzzle, but curl, fetch, requests or any language’s standard HTTP library works exactly the same.
Testing locally
  • While developing, a tunnel such as ngrok gives your local machine a public HTTPS URL you can use as the return_url.
  • Keep the key in SANDBOX mode until your full flow — token, create, redirect, verify — works end to end.