Onboarding API — PJ

Before registering a partner through the API, confirm that your marketplace itself is already accredited with Getnet. This accreditation is a manual process, handled directly with Getnet, and is a prerequisite for every endpoint below.

Verify Whether the Partner Already Exists

Before registering a partner, check whether their CNPJ is already registered under your marketplace. Partners can also register directly through Getnet's Portal Minha Conta, so this check avoids a creation call being rejected for duplication.

1. Send a GET request to /v2/mgm/pj/consult/{merchant_id}/{cnpj}, replacing merchant_id with your marketplace's identification number at Getnet (EC, Merchant Establishment) and cnpj with the partner's CNPJ.
2. Include the Authorization header with the access token, in the format Bearer <token>.
3. Check the response code:
   • 200: the partner is already registered. The response body returns the partner's current data inside an array.
   • 206: no eligible registration was returned for that CNPJ. Rejected, declined, or de-accredited registrations may not appear in this query and may be handled later as a retry or reuse. Continue at Create the Partner's Pre-Registration.
   • 400, 401, 404, 500: see Check the Response Codes, further below.

CNPJ Format

• Numeric: 14 digits.
• Alphanumeric: the first 8 positions and the next 4 can be letters or numbers. The last 2 positions (check digits) must be numeric. Letters are automatically normalized to uppercase.

In both formats, the relationship between a headquarters and its branches is kept through the CNPJ's root digits.

Create the Partner's Pre-Registration

1. Set the Authorization header with the access token, in the format Bearer <token>.
2. Build the request body with the required fields listed in the table below.
3. Send the request and check the response code in the Check the Response Codes table, further below.

Required Fields

Optional Fields

Phone Rules

• Mobile: 9 digits, with the first digit being 9 for most area codes (DDDs). DDDs 41, 46, 47, 48, 49, 51, 53, 54, 55, 61, 62, 64, 65, 66, 67, 68, and 69 have their own rules.
• Landline: 8 digits, with the first digit 2, 3, 4, or 5. The DDD must appear on ANATEL's list.

Address Rules

• street can't be empty or null.
• number must contain digits only, if provided. Use 0 or null if the address has no number.
• postal_code must be a valid CEP (postal code).
• city, state, and district are required.
• suite is also part of the address object (e.g. apartment or unit number).

Bank Account Rules

• type_accounts distinguishes a single bank account (unique_account) from brand-specific accounts (custom_accounts). Send only the object that matches type_accounts; never send unique_account and custom_accounts together.
• unique_account: account_type, bank (bank code), agency, agency_digit, account, account_digit.
• custom_accounts: an array with at least one item, with the same fields as unique_account, plus brand (e.g. "Mastercard").

Commission Rules

• brand, product, and payment_plan are required.
• Set commission_percentage or commission_value, not both. If commission_percentage is greater than 0, commission_value must be 0 or null.
• commission_percentage accepts values between 0.00 and 100.00. commission_value must be 0.00 or greater.

List the Available Payment Plans

Check the Partner's Registration Status

Update the Partner's Registration

De-Accredit the Partner

Check the Response Codes

These calls cover the legal-entity partner's full lifecycle, from initial verification to de-accreditation. Always validate the result using the response codes above.

Next Steps

1. Onboarding API — PF: the same flow for individual partners.
2. Payment Acceptance: see how to process sales once the partner is registered.