Transfer to another arrangement

Transfer to another arrangement refers to the transfer of funds from a card to an SDWO account, followed by a transfer to another arrangement (e.g., Pix or another SDWO). For example, when adding balance to your digital wallet (or someone else's), and choosing the option to pay with Pix but the Pix debit will be made from a branded card (either credit or debit).

See below for an example of a SDWO request of the type transfer to another arrangement:

Request

{
    "MerchantOrderId": "2012345678",
    "Customer": {
        "Name": "Aline de Souza",
        "Identity": "12345678900",
        "IdentityType": "CPF"
    },
    "Payment": {
        "Type": "CreditCard",
        "Amount": 15700,
        "Installments": 1,
        "SoftDescriptor": "CARTEIRA*NOMELOJA",
        "CreditCard": {
            "CardNumber": "4532110000001234",
            "Holder": "Aline de Souza",
            "Brand": "Visa",
            "SecurityCode": "123",
            "ExpirationDate": "12/2030"
        },
        "Wallet": {
            "PlatformOperator": "ABC",
            "TransferType": "Pix",
            "ReceiverData": {
                "Name": "Alan de Souza",
                "Identity": "11122233344",
                "CompanyName": "NOME RAZAO SOCIAL"
            },
            "AdditionalData": {
                "Mcc": "6054",
                "CashIn": true
            }
        }
    }
}

Header parameters

PropertyDescriptionTypeSizeRequired
MerchantIdMerchant identifier in Gateway de Pagamento.Text36Yes
MerchantKeyPublic key for dual authentication in Gateway de Pagamento.Text40Yes
RequestIdRequest identifier, used when the merchant uses different servers for each GET/POST/PUT.Text36No

Body parameters

Check the standard credit or debit card request to verify other optional fields. The table below presents the exclusive parameters for SDWO transactions of the type transfer to another arrangement.

ParameterDescriptionTypeSizeRequired?
MerchantOrderIdOrder 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.
string50Yes
Customer.NameBuyer's name.
Note: Only characters a-z, A-Z are allowed. Special characters and numbers are not permitted.
string255Yes
Customer.IdentityBuyer's CPF or CNPJ number.text14Yes, if the holder is a legal entity (CNPJ).
Customer.IdentityTypeType of buyer's identification document (CPF/CNPJ).text255Yes, if the holder is a legal entity (CNPJ).
Payment.TypeType of payment method. Default value: CreditCard.string-Yes
Payment.AmountOrder amount (sent in cents).integer15Yes
Payment.InstallmentsNumber of installments. For installment transactions, the number of installments will always be greater than 1.integer2Yes
SoftDescriptorText that will be printed on the cardholder's bank statement. Special characters are not allowed. Must be filled in the format WalletName*merchantname.text13Yes
Payment.CreditCard.CardNumberBuyer's card number.string19Yes
Payment.CreditCard.HolderBuyer's name printed on the card. Special characters or accents are not accepted.string25Yes
Payment.CreditCard.BrandCard brand. Possible values: Visa / Master / Amex / Elo / Aura / JCB / Diners / Discover.string10Yes
Payment.CreditCard.SecurityCodeSecurity code printed on the back of the card.string4Yes
Payment.CreditCard.ExpirationDateExpiration date printed on the card. Example: MM/YYYY.string7Yes
Payment.Wallet.PlatformOperatorAcronym of the wallet registered at Cielo as a digital wallet (check your acronym with your account manager).string (text)3Yes
Payment.Wallet.TransferTypeType of transfer to another arrangement. Possible values:
-"Pix" for Pix
-"Exchange" for exchange
-"Others" for another arrangement (another wallet).
text-Yes
Payment.Wallet.ReceiverData.NameName of the receiving customer or establishment.text70Yes
Payment.Wallet.ReceiverData.IdentityCPF or CNPJ number of the receiver.text14Yes
Payment.Wallet.ReceiverData.CompanyNameCorporate name of the receiving establishment.text40Yes, if the receiving customer is a legal entity (CNPJ).
Payment.Wallet.AdditionalData.MccDigital wallet MCC for fund transfer transactions to another arrangement, according to the card brand. See the MCC Table for SDWO Fund Transfer Arrangement.string (numeric)4Yes
Payment.Wallet.AdditionalData.CashInSend as true.boolean-Yes