Subacquirer Routing#
This guide shows how Tuna vendor fields are mapped when routing transactions to subacquirer integrations.
Routes used for subacquirer flows:
- Rede
- Cielo
- PagBank
note
Tuna-managed routing paths continue to run independently from subacquirer flows.
Vendor fields expected by Tuna Init#
Use the vendor object in api/Payment/Init with these key fields:
- Name
- Phone
- WebsiteUrl
- Code
- MCC
- Document
- DocumentType
- Address
Rede mapping#
| Provider payload field | Tuna vendor field |
|---|---|
| paymentFacilitatorID | Not mapped from vendor (Tuna/Rede credential) |
| marketplaceId | Not mapped from vendor (Tuna/Rede credential) |
| subMerchant.subMerchantID | Document (fallback identifier behavior) |
| subMerchant.mcc | MCC |
| subMerchant.address | Address.Street |
| subMerchant.city | Address.City |
| subMerchant.state | Address.State |
| subMerchant.country | Constant BRA (hardcoded) |
| subMerchant.cep | Address.PostalCode |
| subMerchant.taxIdNumber or subMerchant.cnpj | Document |
| subMerchant.merchantTaxIdName | Name |
Cielo mapping#
| Provider payload field | Tuna vendor field |
|---|---|
| Payment.PaymentFacilitator.EstablishmentCode | Not mapped from vendor (Cielo facilitator credential) |
| Payment.PaymentFacilitator.SubEstablishment.EstablishmentCode | Code |
| Payment.PaymentFacilitator.SubEstablishment.Identity | Document |
| Payment.PaymentFacilitator.SubEstablishment.Mcc | MCC |
| Payment.PaymentFacilitator.SubEstablishment.Address | Address.Street |
| Payment.PaymentFacilitator.SubEstablishment.City | Address.City |
| Payment.PaymentFacilitator.SubEstablishment.State | Address.State |
| Payment.PaymentFacilitator.SubEstablishment.CountryCode | Constant BRA (hardcoded by Cielo integration) |
| Payment.PaymentFacilitator.SubEstablishment.PostalCode | Address.PostalCode |
| Payment.PaymentFacilitator.SubEstablishment.PhoneNumber | Phone |
| Payment.SoftDescriptor | Derived from payment descriptor settings and can fall back to vendor Name in subacquirer flows |
Identity is populated from vendor Document. DocumentType is not a direct Cielo payload field and is inferred by identity format in Tuna.
PagBank mapping#
| Provider payload field | Tuna vendor field |
|---|---|
| charges[].sub_merchant.reference_id | Code |
| charges[].sub_merchant.name | Name |
| charges[].sub_merchant.tax_id | Document |
| charges[].sub_merchant.mcc | MCC |
| charges[].sub_merchant.address.street | Address.Street |
| charges[].sub_merchant.address.number | Address.Number |
| charges[].sub_merchant.address.locality | Address.Neighborhood |
| charges[].sub_merchant.address.city | Address.City |
| charges[].sub_merchant.address.region_code | Address.State |
| charges[].sub_merchant.address.country | Constant BRA (hardcoded by PagBank integration) |
| charges[].sub_merchant.address.postal_code | Address.PostalCode |
| charges[].sub_merchant.phones[].country | Phone (country code component) |
| charges[].sub_merchant.phones[].area | Phone (area code component) |
| charges[].sub_merchant.phones[].number | Phone (number component) |
| charges[].sub_merchant.phones[].type | Phone (type metadata) |
| charges[].sub_merchant.url | WebsiteUrl |
PagBank caveat: sub_merchant is only sent when minimum vendor fields are present and Document exists.
Forwarding behavior#
When a payment starts from Payment Link, vendor/submerchant data captured in link creation and add-payment-method steps is forwarded to Payment Init and then consumed by subacquirer routes when applicable.
Support and enablement#
Tuna currently supports subacquirer routing with Rede, Cielo, and PagBank.
If you need support for additional acquirers, contact Tuna Support or your account team to evaluate enablement for your environment.