Prepare an OpenAPI integration
Set up authorization, limits and idempotent requests.
Use your own API key
Create or request the required API permissions in Developer settings, with the necessary egress rules and limits. Never put keys in a public webpage or give them to third parties. Subaccounts also need the relevant authorization from their main account.
Keep requests traceable
Use the idempotency key required by each endpoint and store the request and order IDs. Reuse the same key when retrying the same operation. Query an existing order after a timeout. Sign in to the current developer documentation for exact paths, fields and errors.
Prepare permissions
Open the developer area using your own approved account.
- Check feature access; subaccounts also need permission from the main account.
- Create a Key with the required scope and configure IP and operation or funding limits.
- Store credentials on your server, not in public web pages.
- Use the current developer documentation for exact routes, authentication and error codes.
Manual illustrations show the entry point and never contain a usable API key.
A minimal integration sequence
Implement queries and idempotency before connecting write operations.
- Verify authentication and IP restrictions using a read-only endpoint.
- Keep one stable idempotency key for the same business request.
- Store the request identifier and platform order ID.
- Confirm current status through queries, then integrate callbacks and support workflows.
Troubleshoot failures
Check HTTP status, business error code, permissions, limits and idempotency key. A timeout does not establish business failure. Query the existing order before retrying and send support a redacted request, identifiers and time, never credentials or full card details.