API Partner vs. Merchant Context

Created by Richard Moore, Modified on Mon, 4 Dec, 2023 at 9:51 AM by Richard Moore

What is the difference between a Partner and Merchant?


A Partner, or organization as it is represented in our API, is an entity that will onboard sub-merchants onto Exact's PayFac-as-a-Service platform. It will then integrate with a series of APIs to manage various payments functions on behalf of its sub-merchant portfolio.


A Merchant, or account as it is represented in our API, is either onboarded as a direct merchant under Exact Payments organization, or as a sub-merchant under a Partner. 


Which API context do I use, Partner or Merchant?


The Partner context is meant to be invoked by a Partner (Organization) on behalf of a given sub-Merchant (account) in the request URL.


The Merchant context is meant to be invoked by a standalone merchant without a Partner relationship, or by a sub-merchant beneath a Partner, in the request URL.


What is the difference in authentication methods?


The Partner (organization) must authenticate using the Partner or organization token.

{{baseUrl}}/application/{{applicationId}}/organization/{{organizationId}}/token


The Merchant (account) must authenticate using the Merchant or account token.

{{baseUrl}}/account/{{accountId}}/token


Partner token vs Merchant Token request example:


Partner Context Requests contain the accountId of the sub-Merchant, for example:

{{baseUrl}}/account/{{accountId}}/payments


Merchant Context Requests do not contain an accountId, as they are limited to a single account: 

{{baseUrl}}/payments

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article