Authorization with Token
Authorization with the Google Pay token happens in the same way as standard credit card authorization. However, instead of providing card details openly, the token received by Google Pay must be provided, as shown in the example:
The following integration should be used when sending encrypted card data. If the merchant sends the authorization request with decrypted card data, please refer to Decrypted card .
Request
{
"MerchantOrderId": "2014111708",
"Customer": {
(…)
},
"Payment": {
"Type": "CreditCard",
"Amount": 100,
"Installments": 1,
"Wallet": {
"Type": "AndroidPay",
"WalletKey": "{\"encryptedMessage\": \"ZW5jcnlwdGVkTWVzc2FnZQ==\",\"ephemeralPublicKey\": \"ZXBoZW1lcmFsUHVibGljS2V5\",\"tag\": \"c2lnbmF0dXJl\"}",
"AdditionalData": {
"Signature": "ZXBoZW1lcmFsUHVibGljS2V5"
}
}
}
}
| Header Parameters | Description | Type and Size |
|---|---|---|
MerchantId | Store identifier at Cielo 3.0. For the Sandbox environment, use 63D6ACCB-2734-4236-AB5D-843A9DAC44C7. | GUID (36) |
MerchantKey | API key for Cielo 3.0. For the Sandbox environment, use ZCVHDJWKTGOZXADDYJFURIDIKHEMRYQAQDYEJMQK. | String (24) |
| Parameters | Description | Type and size |
|---|---|---|
MerchantOrderId | Order identification number. | String (50) |
Customer | Node with the shopper's data. | Refer to API E-commerce Cielo{:target="_blank"}. |
Payment.Type | Payment method type. Possible values: "CreditCard" / "DebitCard". | String (100) |
Payment.Amount | Transaction amount in cents. | Number (15) |
Payment.Installments | Number of installments. | Number (2) |
Payment.Wallet.Type | allet provider name. For Google Pay, use "AndroidPay". | String (15) |
Payment.Wallet.WalletKey | Provide the signedMessage received from Google Pay. | String |
Payment.Wallet.AdditionalData.Signature | Provide the signature received from Google Pay. | String |
The wallet authorization response will have the same fields presented in Create an e-wallet payment using encrypted card, however with the addition of the Payment.Wallet node repeating the same fields used in the authorization, as described above.
Updated 2 days ago