All calls to Network Tokenization must include the following API headers:
HeaderFormatExampleDescription
AuthorizationStringBearer <api key>The API key you created during onboarding
X-Merchant-IDString”9bb8592c-cb99-48f7-907e-f97de930fc5c”Identifies the merchant making the request
The first header is used for authentication, and the X-Merchant-ID clarifies which merchant sent the request. This merchant identification is especially important for platform providers; learn more below .

​
Authentication

The Pagos platform uses API keys to authenticate requests to all our services. See our API Authentication guide for full instructions on generating API keys and authenticating with the Pagos APIs.

​
Merchant Identification

To better support Pagos users with merchant-to-platform hierarchies, Network Tokenization includes a X-Merchant-ID attribute in the header that sits underneath the API User. The relationship between API User and merchant is 1..n; an API User can have n merchants but a merchant will be associated with only one API User. Pagos uses this merchant ID to pull the applicable network-specific MIDs to send to the networks for account updates. We’ll assign this unique merchant ID to you at the time of onboarding. If your business doesn’t operate as a platform, you’ll always use the same ID in the header of each call. Any webhook that echos back to your business will also include this unique merchant identifier.