Colombia
One-Time Payment
Subscriptions
Payouts
Ecuador
One-Time Payment
Subscriptions
Mexico
One-Time Payment
Subscriptions
Peru
One-Time Payment
Subscriptions

Card

With this integration, the customer will be able to perform One-Time Payment transactions using a credit card.

Find here the information step by step:

Looking for a plugin?

Check our plugin documentation and install it on a few clicks on your E-commerce website

Frontend Integration

  1. Import Cajita in your HTML by adding the src and the form tag (where you will get the kushkiToken). Check Cajita Reference here
  1. Setup Cajita as shown in the script for Card
  1. Click on the PAY button to get the kushkiToken from Cajita´s submit event (action confirm with POST method)

The token has a lifespan of 30 minutes and it can be used only once

Backend Integration

  1. Request the charge from backend using our API. Check API Reference
  1. Show messages on screen to inform the customer whether the transaction was approved or declined depending on the response from step 4

Sandbox

Kushki allows to simulate successful and failed transactions. To test your integration, use the following information:

  • Approved Transaction
    Card number: 5451951574925480

  • Declined transaction in token request
    Card number: 4574441215190335

  • Declined transaction in charge request
    Card number: 4349003000047015

The expiration date can be any future date and the CVV can be any 3-digit value.


Certification Checklist

Take into account the following guidelines to pass the technical certification (required to get production credentials):

  1. Correct taxes calculations
  2. Do not store any sensitive card data on your database (full card number, CVV, or expiration date)
  3. Messages on screen according to Kushki’s responses
  4. Save all responses (needed in case you asked for support)
  5. Make sure to send in the body of the request all the required variables specified in the API reference

Form validations (not applicable when using Cajita):

  1. Cardholder name is required
  2. Card number field allows only numbers
  3. Card number field allows a maximum of 16 digits (could be less)
  4. Card number is required
  5. CVV field allows only numbers
  6. CVV field allows a maximum of 4 digits (could be 3)
  7. CVV is required
  8. The CVV is masked, so it cannot be read, by replacing each character with symbols such as asterisks (*) or dots (•)
  9. Expiration date is a valid date (current month and year, or future)
  10. Expiration date is required
  11. The PAY button is disabled after the first click
  12. Kushki’s logo is visible. You can download the resource here