Underwrite and configure a Merchant with payment processing capability on the Global Payments system.
Bearer access token value used to authorize and access the API. Must always begin with the string "Bearer".
Format of the message body.
The version of the API to execute the request.
Integrator generated value submitted in the request header that is checked to ensure the same value has not been seen in the last 24 hours. It is used to ensure idempotency is maintained with this action.
This is a label to identify the merchant
Indicates the type of organization entitiy being boarded. Must always be set to MERCHANT.
MERCHANT - The entity is selling their own goods and servicesPARTNER - The entity managing multiple merchants within their integration.The legal business name of the merchant being boarded.
The merchant's DBA (Doing Business As) name or the alternate name the merchant may be known as.
A four-digit number used to classify the merchant into an industry or market segment.
The merchant's business website URL
A description of the merchant's business.
This is the business's company registration number.
The currency in which the funds are held in ISO-4217(alpha-3).
The IP the merchant signed up from.
Primary email configured with the merchant. If not provided, communication will be routed to persons.email, where function= APPLICANT
The legal entity or type of business registration of the merchant.
The merchantes tax identification number. For exampe, in the US the (EIN) Employer Identification Number would be used
A client indicated merchant reference identifier.
The preferred language of the merchant.In the format ISO-639-1 (alpha-2) or ISO-639-1 (alpha-2)_ISO-3166(alpha-2)
Describes the pricing profile the merchant is to be configured for. This will drive the services, pricing and limits configured for merchant boarding
Specified time to close the Batch