Credit and Debit cards

Learn how to integrate your solution to process credit or debit card payments.

Note

We only offer support for merchants in Paraguay through the Gateway model, and we send the invoice to them from Uruguay.

Considerations

The acquirer does not accept online returns, only cancellations are allowed within the same business day (which ends at 7:59 p.m. Paraguay time). refunds must be processed manually by the merchant.

Request parameters

You need to include specific fields for this payment method to work correctly. Check the Purchase operation article for details on authentication, languages of the response, and basic purchase parameters such as amount and currency.

Property	Type	Mandatory?	Description
`TrxToken`	`string`	Yes	The token that identifies the customer’s card. For more information about how to create the token, refer to Customers.
`TargetCountryISO`	`string`	Yes	Indicate the destination country.
`Customer` → `Email`	`string`	Yes	Customer’s email.
`Customer` → `FirstName`	`string`	No	Customer’s first name.
`Customer` → `LastName`	`string`	No	Customer’s last name.
`Customer` → `DocumentType`	`string`	No	Customer’s document type. Refer to the Document types table to see the possible values.
`Customer` → `DocumentNumber`	`string`	No	Customer’s Document Number.
`Customer` → `PhoneNumber`	`string`	No	Customer’s phone number.
`Customer` → `Address` → `Country`	`string`	No	Customer’s Country.
`Customer` → `Address` → `State`	`string`	No^*	Customer’s State.
`Customer` → `Address` → `City`	`string`	No	Customer’s City.
`Customer` → `Address` → `AddressDetail`	`string`	No	Customer’s Address Detail.
`Customer` → `Address` → `PostalCode`	`string`	No	Customer’s Postal Code.

Info

Remember that for the Anti-fraud system’s correct functioning, we suggest sending additional data described in the section Anti-fraud.

Request example

{
    "TrxToken": "OT__6dHAgJo6qeg62qIroA7H7_f_NWZZ6IEx4jiYpVJ8SzQ_",
    "UniqueID": "paymentID3022",
    "Capture": true,
    "TargetCountryISO": "AR",
    "Currency": "ARS",
    "Amount": 25000,
    "Installments": 1,
    "Order": "CH2023-001",
    "Description": "Purchase test",
    "Customer": {
        "FirstName": "Joao",
        "LastName": "Silva",
        "ReferenceCode": "JS-001",
        "PhoneNumber": "11987654321",
        "DocumentNumber": "12345678901",
        "DocumentType": "DNI.AR",
        "Email": "joao.silva@example.com",
        "Address": {
            "Country": "AR",
            "City": "Bs As",
            "State": "C",
            "PostalCode": "01310-200",
            "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": "PYG",
    "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"
    }
}

Risk index information (local credit cards)

The acquirer processes the transactions and establishes a risk index associated with transactions with local credit cards. This information must be processed by the merchant to ensure that the transaction is legitimate and to be able to process the order or cancel it if necessary.

The acquirer reports the risk index as an error code in the response (within the Transaction object); even though the status is Approved, you must validate the ErrorCode field, which may have one of the following values:

RSK01: The acquirer marked the transaction with a low risk of fraud. You can process it normally.
RSK02: The acquirer marked the transaction with a medium risk of fraud. You decide the actions to take in this case.
RSK03: The acquirer marked the transaction with a high risk of fraud. We suggest to verify the data, including direct contact with the end customer.

You are responsible for processing and managing the risk responses, and the gateway will only report the index established by the acquirer.

Last modified December 20, 2024