MasterID provides one live API credential pair per workspace. There is no sandbox in this release. Use approved test identities only when testing live services.
1
Generate credentials and record your Merchant ID
Open the Developer Console and generate an API Key and API Secret. Securely store both values when first shown. Secrets cannot be recovered after their first display is closed. Record your Merchant ID, but note that it does not authenticate requests.
2
Set environment variables
Keep credentials in your server’s secret store and read them from environment variables. Never include them in browser JavaScript, public repositories, URLs, analytics, or application logs.
.env
3
Call GET /catalog for supported products
List the verification products available to your workspace, their required fields, and wallet charges.Use the response to determine which product and fields you need for your use case.
4
Check GET /wallet before submitting
Ensure your workspace has sufficient funds before creating a charged verification.
5
Request consent wording
Before submitting a verification, obtain the data subject’s lawful authorisation. Request exact consent wording using the same fields you intend to submit.Present the returned
consentText to the data subject for genuine confirmation. If the identity details change, request fresh wording.6
Submit the verification with Idempotency-Key
Include the exact consent text and set
consentConfirmed to true. Include a unique Idempotency-Key header. Store the returned sessionId.7
Poll for the result or wait for a webhook
A pending response returns HTTP 202. Poll
GET /verifications/{sessionId} no more frequently than every 15 seconds, or accept a signed verification.completed webhook.8
Activate your merchant account before collecting payments
Complete merchant activation in the MasterID app before you create collection requests. The Merchant ID alone does not enable collections.
End-to-end example
The following Node.js and Python scripts request consent, prompt for confirmation, submit a verification, and poll every 15 seconds until a final status is returned.Next steps
- Authentication: learn how to protect and rotate credentials.
- Products: review all supported verification products and required fields.
- Guides: explore detailed flows for verifications, collections, and webhooks.
- API reference: browse endpoint-level documentation.

