Purchase Arrangement SDWO

ℹ️
Alphanumeric CNPJs will be implemented by the Brazilian Federal Revenue Service in July 2026
This change applies only to new registrations. There will be no changes to existing CNPJs.
The alphanumeric CNPJ is already supported by Cielo, with no changes required to your integration.
We recommend checking whether adjustments are needed in your merchant’s own checkout systems.

The transfer within the purchase arrangement refers to the use of a card (card-not-present) linked to an SDWO digital wallet to buy a good or service from a merchant enabled to accept the SDWO payment brand. It is used, for example, in purchases of goods or services via QR Code, purchases made through the online payment button (checkout), or purchases made within SDWO itself.

See below an example of an SDWO request for the Purchase Arrangement type:

Request

Ambiente	Método	Endpoint
Sandbox	post	`https://apisandbox.braspag.com.br/v2/sales/`
Produção	post	`https://api.braspag.com.br/v2/sales/`

{  
  "MerchantOrderId": "1234567897",
  "Customer": {
    "Name": "Aline de Souza",
    "Identity": "12345678900",
    "IdentityType": "CPF"
  },
  "Payment": {
    "Provider":"Cielo30",
    "Type": "CreditCard",
    "Amount": 100,
    "Installments": 1,
    "SoftDescriptor": "PAY*LOJATESTE",
    "CreditCard": {
      "CardNumber": "5067470000003000",
      "Holder": "Cielo",
      "ExpirationDate": "01/2030",
      "SecurityCode": "480",
      "Brand": "Elo"
    },
    "Wallet": {
      "PlatformOperator": "PAY",
      "TransferType": "PurchaseArrangement",
      "ReceiverData": {
        "Identity": "13730109000126",
        "Name": "Razao Social LTDA",
        "CompanyName": "Razao Social LTDA",
        "WalletId": "12345678900",
        "CountryCode": "076"
      },
      "AdditionalData": {
        "Mcc": "6540"
      }
    }
  }
}

Header parameters

Property	Description	Type	Size	Required
`MerchantId`	Merchant identifier in Gateway de Pagamento.	Text	36	Yes
`MerchantKey`	Public key for dual authentication in Gateway de Pagamento.	Text	40	Yes
`RequestId`	Request identifier, used when the merchant uses different servers for each GET/POST/PUT.	Text	36	No

Body parameters

Check the standard credit or debit card request to review the other optional fields. The table below shows the parameters exclusive to an SDWO transaction under the Purchase Arrangement.

ℹ️
Important
Mastercard
Starting 10/30/2026, it will be mandatory to send the sender fields (Customer.Name, Customer.Identity, and Customer.IdentityType) and the recipient fields (Payment.Wallet.ReceiverData.Name, Payment.Wallet.ReceiverData.Identity, and Payment.Wallet.ReceiverData.CompanyName, when applicable).

⚠️
Mandatory Fields for SDWO Purchase Arrangement
For SDWO transactions of the type Purchase Arrangement, it is mandatory to send the following fields:

Payment.Wallet.PlatformOperator;

Payment.Wallet.TransferType;

Payment.Wallet.ReceiverData.Identity;

Payment.Wallet.ReceiverData.Name;

Payment.Wallet.ReceiverData.CompanyName;

Payment.Wallet.ReceiverData.WalletId.

Missing any of these fields may result in the transaction being declined.
For transactions with the Visa card brand, it is also mandatory to send the field Payment.Wallet.ReceiverData.CountryCode.

Parameter	Description	Type	Size	Required?
`MerchantOrderId`	Order identification. Can be used to cancel or query the transaction in the future. Note: Only characters a-z, A-Z, 0-9 are allowed. Special characters and spaces are not permitted.	string	50	Yes
`Customer.Name`	Shopper’s name or business name. Send the individual’s name when `Customer.IdentityType` is CPF or the business name when `Customer.IdentityType` is CNPJ. Warning: Only characters a-z, A-Z are allowed. Special characters and numbers are not permitted.	string	255	Yes
`Customer.Identity`	Shopper's CPF or CNPJ number.	text	14	Yes, if the holder is a legal entity (CNPJ). Allows sending alphanumeric CNPJs.
`Customer.IdentityType`	Type of shopper's identification document (CPF/CNPJ).	text	255	Yes, if the holder is a legal entity (CNPJ).
`Payment.Type`	Type of payment method. Default value: CreditCard.	string		Yes
`Payment.Amount`	Order amount (sent in cents).	integer	15	Yes
`Payment.Installments`	Number of installments. For installment transactions, the number of installments will always be greater than 1.	integer	2	Yes
`Payment.SoftDescriptor`	Text that will be printed on the shopper's bank statement. Special characters are not allowed. Must be filled in the format *WalletNamemerchantname**.	text	13	Yes
`Payment.CreditCard.CardNumber`	Shopper's card number.	string	19	Yes
`Payment.CreditCard.Holder`	Shopper's name printed on the card. Special characters or accents are not accepted.	string	25	Yes
`Payment.CreditCard.Brand`	Card brand. Possible values: Visa / Master / Amex / Elo / Aura / JCB / Diners / Discover.	string	10	Yes
`Payment.CreditCard.SecurityCode`	Security code printed on the back of the card.	string	4	Yes
`Payment.CreditCard.ExpirationDate`	Expiration date printed on the card. Example: MM/YYYY.	string	7	Yes
`Payment.Wallet.PlatformOperator`	Acronym of the wallet registered at Cielo as a digital wallet (check your acronym with your account manager).	string (text)	3	Yes
`Payment.Wallet.TransferType`	Indicates the type of wallet transaction arrangement. For transactions under the purchase arrangement, the fixed value PurchaseArrangement must be sent to identify this arrangement.	string (text)	20	Yes
`Payment.Wallet.ReceiverData.Identity`	CPF or CNPJ number of the receiver.	text	14	Yes
`Payment.Wallet.ReceiverData.Name`	Name of the receiving customer or establishment.	text	70	Yes
`Payment.Wallet.ReceiverData.CompanyName`	Corporate name of the receiving establishment.	text	40	Yes, if the receiving customer is a legal entity (CNPJ).
`Payment.Wallet.ReceiverData.WalletId`	Identifier of the merchant’s or recipient’s digital wallet, when applicable to the arrangement.	text	20	Yes
`Payment.Wallet.ReceiverData.CountryCode`	Recipient’s country code, based on ISO 3166. Example: the ISO 3166 code for Brazil is 076. Access the complete list.	text	3	Yes
`Payment.Wallet.AdditionalData.Mcc`	Digital wallet MCC for toll-type fund transfer transactions, according to the card brand. See the MCC Table for SDWO Fund Transfer Arrangement.	string (numeric)	4	Yes