1. Quick Start
Kushki Docs
English
  • Español
  • English
  • Home
  • Quick Start
    • Frequently Asked Questions
    • Moving to Production
    • Policy for Important API Changes
    • Test Data
    • Error Codes
    • Latest Features
  • Payment Glossary
    • Payments Glossary
  • One-time card payments (Online)
    • Supported card brands
    • Introduction to 3DS
    • Functionalities by business model
    • How do third party commissions work?
    • Integration guide Third Party Commissions
    • One-step Payments
      • How do Card Payments Work?
      • Accept a Card Payment
      • Accept One-Time Payments with OTP
      • OTP Authentication Error Codes
      • Error codes for single card payments
    • Scheduled payments
      • How do Credit or Debit Card Payment Recurring Charges Work?
      • Create a recurring charge
      • Manage your Scheduled Charges
    • Refunds
      • Returns, cancellations, and refunds
    • 3DS Authentication
      • 3DS API integration
      • 3DS integration with kushki.js library
      • 3DS API integration plus kushki.js library
      • 3DS Error Codes
  • Recurring Card Payments (Online)
    • Functionalities by business model
    • Error codes in recurring charges
    • Authenticate your subscriptions with 3DS
    • External subscriptions to Kushki
    • OneClick Payments
      • Accepting One-Click Payments
  • Wire Transfers
    • How do Payments by Wire Transfers Work?
    • Banks and transaction details for bank transfer payments
    • Receive Wire Transfers
    • Check the Status of a Transaction
  • Cash Payments
    • How do Cash Payments Work?
    • Accept a Cash Payment
    • Authorized locations
    • Error Codes for declined cash transaction
  • Plugins
    • Shopify
      • Shopify
      • Plugin Operation
    • VTEX
      • VTEX Integration Guide
  • Payment Links
    • Smartlinks
  • Payment forms and buttons
    • Kajita
      • How Does it Work?
      • Payment Kajitas
    • Payment Button
      • Overview
      • Generate a payment button
  • Branch Offices Management
    • How to Onboard Submerchants via API
  • Notifications
    • Good Practices
    • Check your Webhooks
    • One-time Payments Webhooks
      • Webhook for One-Time Payments made with a card
      • Webhook for One-Time Payments by Wire Transfer
      • Webhook for One-Time Payments in Cash
    • Recurring Payments Webhooks
      • Webhook for Recurring Payments Made with Card
    • Payment button Webhooks
      • Webhooks with Payment Button
    • Smartlinks Webhooks
      • Webhooks with Smartlinks
    • Refunds Webhooks
      • Webhook for Voids and Refunds
      • Chargeback Webhooks
HomeMexico 🇲🇽Ecuador 🇪🇨
Chile 🇨🇱Colombia 🇨🇴Peru 🇵🇪
HomeMexico 🇲🇽Ecuador 🇪🇨
Chile 🇨🇱Colombia 🇨🇴Peru 🇵🇪
Status
Soporte / Support
English
  • Español
  • English
  1. Quick Start

Moving to Production

Read this guide before you start receiving real payments with Kushki
Once you have obtained a certification for your system integration and received your real or productive account, it is important that you first configure your account before receiving payments from your customers.
Importante
Your test account configuration will not be transferred to your productive account,so you must set it up according to your business needs.
To keep in mind
Due to our risk policies, the available payment methods and the integration type may vary once you complete the affiliation. We will tell you how to proceed if this process applies to your merchant.

Front-end configuration#

Depending on your integration technique and type, you must do the following:

Kajita#

In your initialization script, do the following:
1.
Change inTestEnvironment to false
2.
Change merchant_id to the Public Key in your production account
If you use version 2 of Kajita), follow these steps from your Administration Console:
1.
Go to Settings > Integrations > Kajita.
2.
Enable the Production mode option.
3.
Click Publish to confirm that you wish to transfer your Kajita to production mode.
4.
Copy and paste the script of your Kajitas on your website, as explained here.

Kushki.js#

In your Kushki object, do the following:
1.
Change inTestEnvironment to false.
2.
Change merchant_id, to the Public Key of your productive account.

Kushki.js hosted fields#

In your KushkiOptions instance, do the following:
1.
Change inTest to false.
2.
Change publicCredentialId, to the Public Key of your productive account.

iOS#

In your Kushki object, do the following:
1.
Change environment to KushkiEnvironment.production.
2.
Change publicMerchantId, to the Public Key of your productive account.

Android#

In your Kushki object, do the following:
1.
Change the environment to KushkiEnvironment.production.
2.
Change publicMerchantId, to the Public Key of your productive account.

Back end configuration#

Through the service you are using to make the call to our API, do the following:
1.
Remove the suffix -uat from the URL. For example, if the url was https://api-uat.kushkipagos.com/ it will be now https://api.kushkipagos.com.
2.
In the call header, change the default Public Merchant Id or the Private Merchant Id to the respective credentials of your productive account, respectively.
Modificado en 2026-10-14 19:46:07
Anterior
Frequently Asked Questions
Siguiente
Policy for Important API Changes
Built with