1. CARD PRESENT PAYMENTS (API RAW)
EspaƱol
  • EspaƱol
  • English
  • Back to home
  • PerĆŗ šŸ‡µšŸ‡Ŗ
  • Bienvenidos
  • ONLINE PAYMENTS
    • CARD
      • 1. Request a card token
      • 2. Make a charge or deferred charge
      • 3. Void a transaction
      • 4. Refund a transaction
      • 5. Request deferred options
      • 6. Authorize payments
      • 7. Capture an authorized payment
      • 8. Bin Info
      • 9. Bin Info V2
      • 10. Validate OTP
      • 5. Request deferred options
      • 2. Make a charge or deferred charge
      • 1. Request a card token
      • 8. Bin Info
      • 7. Capture an authorized payment
      • 10. Validate OTP
      • 4. Refund a transaction
      • 9. Bin Info V2
      • 6. Authorize payments
      • 3. Void a transaction
    • ONE-CLICK & SCHEDULED PAYMENTS
      • 1. Request a recurring charge token
      • 2. Create a recurring charge
      • 3. Update recurring charge card data
      • 4. Make an One-click payment
      • 5. Cancel a recurring charge
      • 6. Update a recurring charge
      • 7. Add a temporary charge or discount
      • 8. Authorize payments
      • 9. Capture an authorized payment
      • 10. Get recurring charge Info
      • 9. Capture an authorized payment
      • 7. Add a temporary charge or discount
      • 8. Authorize payments
      • 5. Cancel a recurring charge
      • 4. Make an One-click payment
      • 1. Request a recurring charge token
      • 2. Create a recurring charge
      • 10. Get recurring charge Info
      • 6. Update a recurring charge
      • 3. Update recurring charge card data
    • TRANSFER IN
      • 2. Request a Transfer In token
      • 3. Init Transaction
      • 4. Get Status
      • 2. Request a Transfer In token
      • 4. Get Status
      • 3. Init Transaction
    • CASH IN
      • 1. Request a cash in token
      • 2. Init Transaction
      • 3. Transaction Status
      • 2. Init Transaction
      • 1. Request a cash in token
      • 3. Transaction Status
    • SMARTLINKS V2
      • 1. Create a Smartlink
      • 2. Get a Smartlink
      • 3. Delete a Smartlink
      • 4. Update a Smartlink
      • 4. Update a Smartlink
      • 2. Get a Smartlink
      • 3. Delete a Smartlink
      • 1. Create a Smartlink
    • ANALYTICS
      • 1. Get transactions list
      • 1. Get transactions list
    • GATEWAY STATUS
      • 1. Get gateway status
      • 1. Get gateway status
    • COMMISSIONS
      • 1. Get Commission Configuration
      • 1. Get Commission Configuration
    • PAYMENT CREDENTIALS
      • 1. Create a credential
      • 2. Search credentials
      • 3. Advanced search
      • 4. Activate or deactivate
      • 5. Delete credential
      • 6. Update credential
      • 7. Regenerate a credential
      • 6. Update credential
      • 7. Regenerate a credential
      • 2. Search credentials
      • 4. Activate or deactivate
      • 3. Advanced search
      • 1. Create a credential
      • 5. Delete credential
    • PAYMENT BUTTON
      • 1. Create a payment button
      • 1. Create a payment button
    • Request deferred options
  • CARD PRESENT PAYMENTS (API RAW)
    • Test data
    • error-catalog
    • One-time payments
      • Single payment
    • Two-step-payments
      • Authorization and capture
    • Voids & Refunds
      • Void & Reverse
      • Refund a transaction
    • Card information
      • Balance inquiries
      • Get BIN Info
      • BIN info V2
      • Request deferred options
    • Query Transactions
      • Transaction Search
  1. CARD PRESENT PAYMENTS (API RAW)

Voids & Refunds

Integrate the Kushki services to accept card-present payments in your existing flow or create a new flow with the services we offer.
Important
Remember that it is necessary to make the requests through HTTPS using the credentials we provided. It is important that you do not share sensitive data in public places.
Returns can be of three types, according to the day and the time the original transaction and the cancellation request are processed:
Type of serviceDescription
1. ReversalThis request is sent when the expected transaction processing time is exceeded. It is generated when there is a problem in the processing of the transaction and it is unknown if the charge was made. This may be due to a time out problem.
The reversal must be done on the same day as the transaction.
2. VoidIt is generated when it is known that the transaction was processed successfully, but a void request is required.
The void is generated when the refund request is processed on the same day as the transaction was made, before 23:59 (approximate time). This time depends on the cut-off performed by the processor. Up to 3 attempts of refund are made with the processor, and once the void is approved, the charge will be removed from your customer's statement and the deducted amount will be refunded.
3. RefundIt is generated when it is known that the transaction was processed successfully, but a refund request is required.
Refund is generated when the refund request:
- Is processed after 23:59 (approximate time) of the approval day of the transaction.
- When the void request exceeded three attempts.
- When the refund request is made on a different day than the original transaction.
The maximum time allowed to process a refund is 120 days.

1. Reversals#

If there are communication issues or time out, and you need to verify whether a transaction was approved or rejected, you can perform a reverse operation to cancel a transaction.
Note
Reversals are only available on the same day as the transaction was made, before 23:59 for Peru. Please note that you must wait at least 1 minute after the transaction before initiating a reversal.
To reverse a transaction, you need to consume the endpoint /pos/v1/transaction and send Reverse in the transaction_mode field, charge in the transaction_type and the client_transaction_id of the transaction you want to reverse as part of the request body.
Check the example below:
{
  "card": {
    "card_holder_name": "John Doe"
  },
  "amount": {
    "iva": 0,
    "tip": 20,
    "currency": "PEN",
    "extra_taxes": {},
    "subtotal_iva": 0,
    "subtotal_iva0": 200
  },
  "country": "PER",
  "isDeferred": false,
  "is_cashback": false,
  "pos_details": {
    "brand": "SUNMI",
    "model": "P2-EU",
    "version": "Kushki SunmiV1.1.18",
    "location": {
      "latitude": -1.2253600000000002,
      "longitude": -78.61997
    },
    "has_print": true,
    "terminal_id": "PB04209860189"
  },
  "card_details": {
    "tracks": {
      "track_ksn": "FFFF4357486333600003",
      "enc_track2": "2C5E3DC796759FAB00BB11163CC4B69B"
    },
    "enc_tlv": "E9BCEC77FACD77F942E433BE6CD27068F09ADFA082B6AE478D9BDA4EEEAFD3765300FD2EF030CD3A8DD9624E04CDFBC60B4206B9587A1A0DB5820D87D3ACAB9F8B14B35A8B8D7307AEBDCFD9D5DD8EB5DC7BFB729A1E6ABAC08D5C5A064F590F414D560C3EE964449B40D24B09703AE38FF45F328CC03A8A3ABCFBCDF0AFBCDAB674C87AC66CD842E7E9C36B6826ECAC8EB32E5E036787D4B50CD8C43F0C89918A23C396AEE4096805AE52DF13B343A6FDAC864CB27593C65B39B02239B707554357675ED96C3859",
    "pin_ksn": "FFFF4357486333600003",
    "reading_type": "ICC"
  },
  "transaction_mode": "Reverse",
  "transaction_type": "charge",
  "client_transaction_id": "cffd9e13-993d-4d8b-9862-3ac4c0f63dec"
}

Cardless reverse#

Note
This functionality is currently in Beta phase in Peru.
To perform a cardless reverse, send the omit_card field with the value of true as in the following example.
{
    "amount": {
        "currency": "PEN",
        "iva": 0,
        "subtotal_iva": 0,
        "subtotal_iva0": 6000
    },
    "transaction_mode": "Reverse",
    "transaction_type": "charge",
    "client_transaction_id": "6680eadc-6c8d-44aa-8ca0-18e061c1472a",
    "omit_card": true
}
Tip
In the transaction_type field, you must send the type of transaction you want to reverse (capture, charge).

2. Void#

A void is generated when the refund request is processed on the same day as the original transaction, before 23:59 for Peru (approximate time).
To make cancellations, you need to consume the endpoint /pos/v1/transaction and send Void in the transaction_mode, and the transaction_reference of the transaction you want to cancel as part of the request body along with the client_transaction_id of the void transaction.

Cardless void#

Note
This functionality is currently in Beta phase in Peru.
To perform a cardless void, send the omit_card field with the value of true as in the following example.
{
    "amount": {
        "currency": "PEN",
        "iva": 0,
        "subtotal_iva": 0,
        "subtotal_iva0": 60000
    },
    "transaction_mode": "Void",
    "transaction_type": "charge",
    "is_smart_void": true,
    "client_transaction_id": "6680eadc-6c8d-44aa-8ca0-18e061c1472a",
    "transaction_reference": "f2f29080-0214-42c0-95a5-77ecf3434cd7",
    "omit_card": true
}
Tip
In the transaction_type field, you must send the type of transaction you want to void (capture, charge, preAuth, reAuthorization).

3. Refunds#

Through the Kushki API, you can request a refund for a previously authorized transaction or preauthorizations.
This transaction can be identified by its transaction reference number transaction_reference, which is generated once the charge is successfully processed.
For partial refunds, you need to include the amount object in the request.
To request a transaction refund, you need to consume the endpoint pos/v1/refund, send Authorization in the transaction_mode parameter, refund in the transaction_type, and the transaction_reference of the transaction you want to cancel as part of the request body along with the client_transaction_id of the refund transaction.

Cardless refund#

Note
This functionality is currently in Beta phase in Peru.
To perform a cardless refund, send the omit_card field with the value of true as in the following example.
{
    "amount": {
        "currency": "PEN",
        "iva": 0.0,
        "subtotal_iva": 0.0,
        "subtotal_iva0": 600
    },
    "transaction_mode": "Authorization",
    "transaction_type": "refund",
    "client_transaction_id": "6680eadc-6c8d-44aa-8ca0-18e061c1472a",
    "transaction_reference": "f2f29080-0214-42c0-95a5-77ecf3434cd7",
    "omit_card": true
}
Modified atĀ 2026-03-13 14:08:17
Previous
Authorization and capture
Next
Void & Reverse
Built with