Credit and Debit cards

Request parameters

You need to include specific fields for this payment method to work correctly. Check the Request parameters section for details on basic purchase parameters such as amount and currency.

Request example

{
    "TrxToken": "OT__6dHAgJo6qeg62qIroA7H7_f_NWZZ6IEx4jiYpVJ8SzQ_",
    "UniqueID": "paymentID3022",
    "Capture": true,
    "TargetCountryISO": "UY",
    "Currency": "UYU",
    "Amount": 25000,
    "Installments": 1,
    "Order": "CH2023-001",
    "Description": "Purchase Test",
    "Customer": {
        "FirstName": "Joao",
        "LastName": "Silva",
        "ReferenceCode": "JS-001",
        "PhoneNumber": "11987654321",
        "DocumentNumber": "12345672",
        "DocumentType": "CPF.BR",
        "Email": "joao.silva@example.com",
        "Address": {
            "Country": "UY",
            "City": "Montevideo",
            "State": "Mdeo",
            "PostalCode": "11600",
            "AddressDetail": "Avenida Paulista 1000"
        }
    }
}

Response parameters

For more information on the response parameters, please refer to the Response parameters section of the Purchase creation.

Response example

{
    "TransactionId": "79632697147789184",
    "Result": "COMPLETED",
    "Status": "APPROVED",
    "ErrorCode": null,
    "ErrorDescription": null,
    "Created": "2024-08-07T17:51:54.620",
    "AuthorizationDate": "2024-08-07T17:51:56.879",
    "AuthorizationCode": "839936",
    "Amount": 25000,
    "Currency": "UYU",
    "Installments": 1,
    "TaxableAmount": null,
    "Tip": null,
    "Url": "https://api.stage.bamboopayment.com/Purchase/79632697147789184",
    "MetadataOut": null,
    "Action": null,
    "PaymentMethod": {
        "Brand": "Visa",
        "CardOwner": "Joao Silva",
        "Bin": "450799",
        "IssuerBank": "Santander",
        "Type": "CreditCard",
        "Expiration": "203008",
        "Last4": "4905"
    }
}

Testing cards

When generating valid card data for testing, you must first establish which acquirer you want to test and what type of test you want to perform.

Determination of BIN

When setting up an acquirer, the card’s BIN (Bank Identification Number) is also created. This BIN should align with one of the BINs associated with the brands processed by the acquirer. For instance, if you are conducting an integration test with MasterCard, the BIN of the generated card should adhere to the following format: ^ 5 \ [1-5] \ [0-9]*

This format means it must start with the number 5; the second number must be between 1 and 5, then any other number is accepted. For example, the BIN to test can be 510000. The valid Bines in the system and their related acquirer are listed below.

Configured Behaviors for the Payfac model

The behavior of the response will depend on the amount sent. Use the following cards to simulate the different purchase statuses.

Cards without CVV

Configured Behaviors for the Gateway model

The behavior of the response will depend on the termination of the card. Generate the card using the corresponding bin of the brand, and send the following last four digits according to the expected result.

Special features for the Gateway model

• You can make purchases in installments as long as the Issuing Bank has it enabled.
• You can make purchases with Debit Cards as long as the Issuing Bank has it enabled
• Visanet requires the inclusion of the CVV in the customer’s first purchase or the customer’s registration.
  Once you make the registration and obtain the Commerce Token, it is not necessary to request the CVV in future transactions.
• Fiserv requires you to send the CVV, even if you have the Commerce Token. You need to execute Verification Code Request Flow.
  This modality is enabled by default. If you wish to deactivate it, you must negotiate with Fiserv and notify us.
• Creditel and PassCard require that the purchase message include the cardholder’s document and type of document (fields Customer.DocumentTypeId and Customer.DocNumber).
• PassCard requires you to send the CVV, even if you have the Commerce Token. Therefore, you need to execute Verification Code Request Flow.
• When using OCAOneClick2 (OCA Multi-Acquiring), you need to include the IP address of the person making the purchase. To do this, you must send the CustomerIP parameter in the request.

Purchases using MasterCard through OCA

When using MasterCard, sending the device FingerPrint using the SetDeviceFingerPrint method is recommended.

Add this function to the script used for the checkout form (PWCheckOut) to generate and return the value used in the purchases.

In this example, we show how to invoke and obtain the result.

<script type="text/javascript">
    PWCheckout.SetDeviceFingerprint();
</script>

Then, include the token in the purchase creation according to the following scenarios.

• For OneTimeToken, send the device FingerPrint you generate and the OT token.
• For CommerceToken, there are two cases:
  • For Recurring purchases (Without CVV), send the device FingerPrint you generate and the CT token. You can use an existing CT token or generate one.
  • For Purchases with CVV, generating a DeviceFingerPrint is unnecessary since when the customer enters the CVV, the system sends the value generated when displaying the CVV request page. Then, the system generates a Purchase in the Pending state, and you need to redirect the customer to the URL returned in the actionUrl parameter where they enter the CVV.

Last modified December 20, 2024

© Bamboo | All rights reserved 2024