- Authenticating API Calls
- API Keys
- User Access Tokens
- Roles and Permissions
API calls can be authenticated by either providing an API key in the “X-Api-Key” header or by providing a user access token in the “Authorization” header.
Org Accounts accessed with a user access token require the “X-Centrapay-Account” header to be provided. The “X-Centrapay-Account” header specifies the unique identifier of the Centrapay Org Account.
Authenticate with API key
curl https://service.centrapay.com/api/account-memberships \ -H "X-Api-Key: $api_key"
Authenticate with user access token
curl https://service.centrapay.com/api/account-memberships \ -H "Authorization: $jwt"
Authenticate org account with user access token
curl https://service.centrapay.com/api/accounts/Jaim1Cu1Q55uooxSens6yk/bank-accounts \ -H "Authorization: $jwt" \ -H "X-Centrapay-Account: Jaim1Cu1Q55uooxSens6yk"
API Keys provide enduring access to a single Centrapay account.
The Centrapay test merchant API key is available to test creating payment requests:
User access tokens provide time-limited access to all Centrapay accounts for which the user is a member. Access tokens are issued using OIDC code flow via the Centrapay OAuth authorization server and login page at auth.centrapay.com.
After successfully negotiating the OIDC code flow your application will have access to three tokens:
|Id Token||JWT containing user attributes such as id, phone and email.|
|Access Token||JWT granting access to Centrapay APIs. Expires after 1 hour.|
|Refresh Token||Token for OIDC token exchange. Expires after 60 days or when revoked.|
A good starting point for learning more about OIDC is Okta’s OAuth OIDC Illustrated Guide.
When initiating a login request, a valid redirect URI must be provided. To obtain a dedicated OAuth client id with your application’s redirect URI(s) whitelisted please contact Centrapay support. Your callback URI can be for a website (such as “https://yourapp.example.com/oidc-callback”) or mobile app (such as “com.example.yourapp://oidc-callback”).
When handling the OIDC callback, browser based applications should slurp the callback parameters by performing a
location.replace() so they are not available in the browser’s location bar or browsing history. If your application needs to talk directly to service.centrapay.com from a browser then it will also need to be whitelisted for cross-origin requests.
The following table lists the claims which may be be included in a user id token. At minimum, the “sub” claim and one of “phone_number” or “email” will be present.
|sub||Centrapay user id|
|preferred_username||Centrapay user handle|
|phone_number_verified||phone number has been verified (can be used for account recovery)|
|email_verified||email has been verified (can be used for account recovery)|
Users and API keys are assigned a role for their associated Centrapay account(s). The permissions granted to the roles are shown in the table below.
Most permissions apply only to resources owned by the associated account. Some permissions, such as payment-requests:pay, apply globally to all resources regardless of the account the resource belongs to. The global permissions are indicated below with a star (✸).
Some permissions require an additional flag associated to their individual account or the targeted account that owns the resource (they may be the same account). For each permission, if there is a flag associated to it then at least one of them must be met.
|👤||A trusted user flag on the individual account, obtained by verifying a NZ phone number.|
|🧀||An external-asset-issuer subscription on the targeted Account, obtained by contacting centrapay.|
|🗄||The targeted account must be of type org.|
|Permission||Account Owner||Anon Consumer||Merchant Terminal||External Asset Provider|
|invitations: ||✸ ✅|
|invitations: ||✸ ✅|
|payment-requests: ||✸ ✅||✸ ✅||✅|
|payment-requests: ||✸ ✅||✸ ✅||✸ ✅|