Quickstart
Technical Author Note
The Quickstart's single job is to take a developer from zero to one successful test payment — nothing more.
- Prerequisites — where to get sandbox credentials, and the base URL.
- Authenticate — one correctly authenticated request using the finalised auth scheme. This becomes the single source of truth the rest of the docs match.
- Make one test payment — the simplest happy path only: a single
intent: transfersale, no branching. - Read the result — show the response and the
statusfield, noting that HTTP 201 is not success. - Next steps — links onward to Payment Flows and the API Reference.
Note for technical author: Direct API and Hosted Components follow different paths through the quickstart and will need to be covered separately — the authentication step, request body, and how card data is submitted differ between the two. Consider whether this is one page with two tracks, or two separate quickstarts.