Before the first call

What you need before you start

• A sandbox client id and secret. Issued per environment — a sandbox client is not a production client. Ask at Request access.
• Your channel code. It goes on most requests, the platform authorises against it, and some operations behave differently depending on it. Pick it from Channels before you write the client, not after.
• Which card programme you are integrating. Credit, debit and prepaid are separate APIs with separate operations; what they share sits in Common Methods.

The order to read this in

• 01Make your first calltoken, then one operation
• 02Authenticationtokens, users, roles, SSO
• 03Requests and responses356 operations, one shape
• 04Fields on every requestchannel, card keys, pattern id
• 05Errors and failures290 codes
• 06FAQthe questions that get asked

Platform

• domains, services, dataPlatform concepts
• six kinds, six limit rulesCard types and what each one does to a limit
• 3 environmentsEnvironments
• logs, metrics, eventsLogging and monitoring
• cash, instalments, statementsHow money moves
• message types, field mappingISO 8583 to REST
• BNPL, loyalty, AI agentsIntegrations
• what exists, what does notTokenisation
• what you are told unaskedWebhooks, events and fraud

Reference data

• 18 channelsChannels
• 10 statusesCard status transitions
• 69 termsKey terms
• 290 codesError codes
• 70 eventsEvent streams
• 4 releasesChangelog

Learn the domain

• 6 lessonsPayments 101
• 4 conceptsCard model concepts

Build

• 35 capabilitiesCapability map
• 11 guidesBusiness guides
• specs, collections, editorsDeveloper tools
• MCP serverAgent access
• sandbox credentialsRequest access

Then go deeper

Get Started answers how do I call this. Two other sections answer the questions next to it, and neither repeats what is here.

• Integration journeysThe calls in the order a real programme makes them, with the key each step leaves you holding.
• API referenceEvery operation, every field, with a request builder that sends to the sandbox.