Sign in

v1

latestOpenAPI 3.0.02026-07-2352269214.0 KB
Merchant Onboarding

Create a merchant.

The API is synchronous and the Scheme TSP is not involved.

post/merchants

Headers

authorizationstring required

Technical identifier pre-defined at on-boarding that identifies the API consumer. Format shall be the string 'APIKEY' followed by a space and the api key value. </br> Example: APIKEY c03f88fe-01ba-11e8-ba89-0ed5f89f718b

x-correlation-idstring required

Technical identifier used for troubleshooting. </br>It helps on customer support when needed. </br>Each API request must be identified with a unique correlation Id. </br>It correlates the response and the request and eventually a notification if any.

Request body

merchantNamestring required

An unique merchant name that is end user friendly.

Response

Created

merchantIdstring required

Identifier of the merchant provided by Thales at on-boarding.

creationTimestampstring required

Token or binding creation timestamp compliant with ISO 8601.