Payment Facilitators

A payment facilitator sells through sub-merchants and settles their transactions under its own Getnet credential. To meet card-scheme, payment-arrangement, and regulatory requirements, a facilitator identifies the sub-merchant behind every transaction. You send that identification in the data.sub_merchant object of each authorization request.

Availability

Payment facilitators are available for ecommerce (card not present) and card-present transactions:

ModelArgentinaBrazilMexico
Card not present (ecommerce)✅✅✅
Card present-✅-

Enablement

Getnet records payment facilitator status on your credential. No request field turns the product on, so request enablement when you apply for your credential. When your credential is already active but not enabled, contact Integration Support before you integrate.

Object placement

Place sub_merchant at data.sub_merchant, as a sibling of data.payment. Do not nest it inside data.payment or data.additional_data.

Sub-merchant data is transaction data, not a registration. There is no onboarding endpoint, so you send the object on every authorization. The object applies to authorization requests only:

OperationSend data.sub_merchant?
/payments authorizationYes — as a sibling of data.payment.
/payments/combined authorizationYes — in the combined payment data.
/payments/captureNo
/payments/cancelNo
/payments/boletoNo
/payments/qrcode and /payments/qrcode/pixNo
Sub-merchant identification is independent of split-payment fields such as data.additional_data.split. Those fields have their own integration requirements.
The sub_merchant object is not echoed in the payment response.
JSON
{ "idempotency_key": "4c3cbdc2-b41e-4e1c-b7fe-90ed10abd9bb", "order_id": "izgyekkmb8sd", "data": { "amount": 500, "currency": "BRL", "payment": { "payment_method": "CREDIT", "transaction_type": "FULL", "number_installments": 1, "card": { "number": "4012001037141112", "expiration_month": "12", "expiration_year": "30" } }, "sub_merchant": { "identification_code": "9058345", "document_type": "CNPJ", "document_number": "77415914000148", "address": "Dark Tower", "address_number": "207", "district": "Centro", "city": "Sao Paulo", "state": "SP", "postal_code": "90520000", "country_code": "BR", "business_name": "Company Ltd", "acceptor": { "url_address": "https://site.getnet.com.br", "customer_service_phone_number": "551140041234", "tax_id": "77415914000148" } } } }

Required fields

Six fields are required whenever you send the object. The sub_merchant object itself is optional in the API contract — whether you must send it comes from your facilitator credential, not from the request schema. All fields in the tables below sit inside data.sub_merchant.
AttributeTypeDescriptionRequired
identification_codeStringSub-merchant identifier assigned by the facilitator. Maximum 15 characters for Visa and Mastercard. American Express is not subject to this limit. Example: "9058345"Yes
document_typeStringSub-merchant legal document type. Use one of CPF, CNPJ, PASSPORT_BR, DNI, CUIL, CUIT, PASSPORT_AR, RUT, CI, CURP, RFC. Example: "CNPJ"Yes
document_numberStringSub-merchant legal document number. Minimum 5 and maximum 25 characters. Example: "77415914000148"Yes
addressStringSub-merchant street or address. Maximum 60 characters. Example: "Dark Tower"Yes
cityStringSub-merchant city. Maximum 40 characters. Example: "Sao Paulo"Yes
stateStringSub-merchant state or region code. Maximum 3 characters. Example: "SP"Yes

Optional fields

AttributeTypeDescriptionRequired
gateway_idStringSub-merchant gateway identifier. Maximum 11 characters. Argentina, Brazil, and Mexico each derive this value differently. Example: "GW123456"No
postal_codeStringSub-merchant postal code. Maximum 15 characters. Example: "90520000"No
districtStringSub-merchant district or neighborhood. Maximum 60 characters. Example: "Centro"No
country_codeStringSub-merchant ISO country code. Maximum 3 characters. Example: "BR"No
address_numberStringSub-merchant address number. Maximum 6 characters. Example: "207"No
address_complementStringSub-merchant address complement. Maximum 60 characters. Example: "Floor 2"No
business_nameStringSub-merchant business or company name. Maximum 80 characters. Accepts an empty or null value. Example: "Company Ltd"No
foreign_typeStringComposition of sub-merchants in the transaction. Send F for Full Foreign (all sub-merchants are international), P for Partial Foreign (the cart mixes international and national sub-merchants), or D for Full Domestic (all sub-merchants are national).No
foreign_amountIntegerForeign-currency transaction amount in cents. Zero is accepted. Example: 0No
phone_numberStringSub-merchant phone number. Maximum 16 characters. Example: "5511999999999"No
iva_categoryStringIVA/VAT tax category. Maximum 50 characters. Example: "1"No

Acceptor object

The optional acceptor object holds contact information for the sub-merchant.
AttributeTypeDescriptionRequired
acceptor.url_addressStringSub-merchant website URL. Maximum 256 characters. Example: "https://site.getnet.com.br"No
acceptor.customer_service_phone_numberStringSub-merchant customer-service phone number. Maximum 16 characters. Example: "551140041234"No
acceptor.phone_numberStringSub-merchant phone number. Maximum 16 characters. Example: "5511999999999"No
acceptor.additional_contactStringAdditional contact information for the sub-merchant. Maximum 256 characters. Example: "contact@getnet.com.br"No
acceptor.tax_idStringSub-merchant tax identifier. Maximum 35 characters. Example: "77415914000148"No

Address format

The Global API uses a flat address shape. Send address as a string, and send address_number, address_complement, district, city, state, postal_code, and country_code as sibling fields. Do not send address as a nested object.

Country and card-brand requirements

Some markets and card brands add requirements on top of the six base fields.

Country / brandFieldRequirement
Argentina + Mastercardiva_categoryRequired.
Visa or Mastercardidentification_codeMaximum 15 characters.
American Expressidentification_codeNot subject to the 15-character limit.
Argentina, Brazil, Mexicogateway_idDerived by country-specific rules.
information icon
Important: Additional local requirements may apply for some countries and merchants. Confirm with Integration Support which requirements apply to your market.

Validation errors

When a required field is missing, or a value exceeds the limits above, Getnet rejects the request with a validation error naming the offending sub_merchant field.
Country and card-brand rules are evaluated separately from the base contract. A request that satisfies the six required fields can still be declined when a market-specific field is absent — for example a Mastercard transaction in Argentina without iva_category.

For the error response format and the full list of payment error codes, see the Errors reference.