An integration goes much more smoothly when the developer receives the business decisions already made. This article summarizes what you need to define and what to hand over, so the technical work can start without blockers.
Decisions that are up to you
- Payment product: which path you chose (Checkout, plugin, API, or Payment Links) and in which channel it will be used.
- Payment methods: which ones you want to offer — card, SPEI transfer, cash, wallets, or pay-in-installments — and whether you will offer interest-free installments (MSI).
- Expected behavior: what happens after a successful payment (confirmation to the customer, order update) and what happens when a payment fails or remains pending.
- Currency and amounts: typical sales ranges and whether you will handle recurring or one-time payments.
Access and materials you need to provide
- A dedicated user in the Conekta Panel for your developer, with the right role — avoid sharing your password.
- Access to the test environment keys so they can build without the risk of real charges.
- The technical documentation for the chosen product at developers.conekta.com.
- The contact information of the person on your team who will validate the flow before going live.
What to expect from the process
With the complete brief, the developer builds against the test environment, you validate the purchase flow end to end, and only then are the keys switched to production. Understand that boundary in What test and production environments are.