> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jelou.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Usage and configuration

> Add the Conekta node to your Canvas flow, choose the payment experience (WebView or external confirmation), and test payments in the test environment.

Once the integration is connected, the **Conekta** node is available in Canvas and lets you create collection experiences with **embedded WebView** or **external confirmation** within the conversational flow.

> [!TIP]
>
> If you have not installed the integration yet, follow [Connect in Brain Studio](https://docs.jelou.ai/en/guides/integrations/payments/providers/conekta/connect-in-brain-studio.md) first.

***

## Add the node to Canvas

**1. Open your flow in Canvas**

Open in Brain Studio the flow where you want to add Conekta collection.

**2. Add the Conekta node**

Add **Conekta** from the **Canvas** toolbar, in the **Payments** node, or from available payment providers once the integration is installed.

The exact entry point may vary depending on whether you started installation from Marketplace, Jelou Agent, the Payments node in Canvas, or a template.

**3. Connect the node at the collection point**

Connect the Conekta node after the flow already has the amount and purchase confirmation.

**4. Open the configuration panel**

Select the node to open the right sidebar and complete **inputs** and review available **outputs**.

![Conekta node in Canvas with payment outputs and side panel on Payment data tab with Customization disabled](https://mintcdn.com/jelouai/3D3ye1Wdwh66cTgk/assets/images/integraciones/pagos/conekta-nodo-sidebar-configuracion.png?fit=max\&auto=format\&n=3D3ye1Wdwh66cTgk\&q=85\&s=f297b76ce62cf53c5664f4918513802b)

Conekta node in Canvas with the side panel open on Payment data

***

## Configure the node

> [tab] Inputs
>
> ### Payment data
>
> > [accordion] Customization
> >
> > **Customization** `boolean` (default: false)
> >
> > Turn it on to define the messages that accompany the payment button in the conversation.
> >
> > When disabled, Brain Studio uses the default collection message texts.
>
> > [accordion] Header
> >
> > **Header** `string`
> >
> > Title of the payment button message.
> >
> > Shown when **Customization** is enabled. Appears in the message preview.
>
> > [accordion] Content
> >
> > **Content** `string`
> >
> > Main text of the payment button message.
> >
> > Shown when **Customization** is enabled. Appears in the message preview.
>
> > [accordion] Footer
> >
> > **Footer** `string`
> >
> > Closing text of the payment button message.
> >
> > Shown when **Customization** is enabled. Appears in the message preview.
>
> > [accordion] Payment reason
> >
> > **Payment reason** `string` *required*
> >
> > Descriptive text for the charge. Examples: order number, product, service, or internal reference.
> >
> > You can map it from flow variables, for example `{{$memory.paymentBreakdown.summary}}`.
>
> > [accordion] Taxable amount
> >
> > **Taxable amount** `number` *required*
> >
> > Amount subject to VAT. Numbers only.
> >
> > You can map it from flow variables.
>
> > [accordion] Tax-free amount
> >
> > **Tax-free amount** `number` *required*
> >
> > Tax-exempt amount. If not applicable, use `0`. Numbers only.
> >
> > You can map it from flow variables.
>
> > [accordion] Cardholder first name
> >
> > **Cardholder first name** `string`
> >
> > First name of the person or company holding the payment.
> >
> > Applies when **Payment experience** is **External Confirmation Payment**. If the flow does not send it, the conversational agent asks the payer directly.
>
> > [accordion] Cardholder last name
> >
> > **Cardholder last name** `string`
> >
> > Last name of the person holding the payment.
> >
> > Applies when **Payment experience** is **External Confirmation Payment**.
>
> > [accordion] Document or tax ID number
> >
> > **Document or tax ID number** `string`
> >
> > This field appears on the node because it is shared with Wompi, but **Conekta does not use it**: you can leave it empty. The agent does not ask the payer for it either.
>
> > [accordion] Email
> >
> > **Email** `string`
> >
> > Email of the person holding the payment.
> >
> > Applies when **Payment experience** is **External Confirmation Payment**.
>
> ![Conekta node side panel on Payment data tab with Customization enabled, Header, Content, Footer fields, message preview, and charge amounts](https://mintcdn.com/jelouai/3D3ye1Wdwh66cTgk/assets/images/integraciones/pagos/conekta-nodo-datos-del-pago.png?fit=max\&auto=format\&n=3D3ye1Wdwh66cTgk\&q=85\&s=84d6caefc182d0da0c3220313ec31a81)
>
> Payment data with payment button customization enabled
>
> ![Conekta node side panel on the Payment data tab showing the Cardholder first name, Cardholder last name, Document or tax ID number, and Email fields](https://mintcdn.com/jelouai/1_JmEPMrIr40GNhs/assets/images/integraciones/pagos/conekta-nodo-datos-pago-confirmacion-externa.png?fit=max\&auto=format\&n=1_JmEPMrIr40GNhs\&q=85\&s=db4cc16b73420ff783adc215c5b3d241)
>
> Payment data with the External Confirmation Payment experience: Cardholder first name, Cardholder last name, Document or tax ID number, and Email fields
>
> > [!NOTE]
> >
> > With **Customization** disabled, the panel shows the charge fields directly. The node in Canvas exposes the outputs **Successful payment**, **Pending payment**, **Payment message sent**, **Failed payment**, and **Error**.
>
> ### Advanced
>
> > [accordion] Environment
> >
> > The **Environment** block shows whether Conekta runs in **Development** or **Production**.
> >
> > If the integration is in **Development**, you can start the **Go live** flow from there.
> >
> > If the integration is in **Production**, the block reflects that Conekta already operates with production credentials.
> >
> > > [!WARNING]
> > >
> > > The environment depends on installed credentials. Do not go live without preparing production credentials.
>
> > [accordion] Payment experience
> >
> > **Payment experience** `string` *required*
> >
> > Defines how the payer completes the transaction. Available options:
> >
> > * **WebView Payment** — opens the Conekta checkout as embedded WebView within the conversation.
> > * **External Confirmation Payment** — a conversational agent guides the payer to complete the payment via **approval in the BBVA Wallet app** or **SPEI code**, outside WhatsApp.
> >
> > ![Conekta node Advanced tab showing the Payment experience field with the WebView Payment and External Confirmation Payment options](https://mintcdn.com/jelouai/1_JmEPMrIr40GNhs/assets/images/integraciones/pagos/conekta-nodo-avanzado-experiencia-pago.png?fit=max\&auto=format\&n=1_JmEPMrIr40GNhs\&q=85\&s=38759431566fa544c8d60ac8c23093ac)
> >
> > Payment experience field on the Conekta node's Advanced tab
>
> > [accordion] Payment button expiration
> >
> > **Payment button expiration** `number`
> >
> > Defines how long the payment button remains valid after being sent.
> >
> > Available values depend on the configuration visible in Brain Studio.
>
> > [accordion] Currency
> >
> > **Currency** `string` *required*
> >
> > Defines the collection currency.
> >
> > For Conekta Mexico, you will normally use `MXN`.
>
> > [accordion] VAT percentage
> >
> > **VAT percentage** `number`
> >
> > Defines the VAT percentage applied to the collection operation.
>
> > [accordion] Payment metadata
> >
> > **Payment metadata** `string`
> >
> > Optional field to store internal reference such as order ID, sequence number, user ID, or booking ID.
>
> > [accordion] Save response
> >
> > **Save response** `string`
> >
> > Defines the memory variable name where Brain Studio will store the node response.
> >
> > The response will be available in later flow nodes, for example `{{$memory.paymentResponse}}`.
> >
> > > [!TIP]
> > >
> > > Useful for traceability, later validations, or flow decisions.
>
> ![Conekta node side panel showing the Advanced tab with button expiration, MXN currency, VAT, metadata, and save response](https://mintcdn.com/jelouai/3D3ye1Wdwh66cTgk/assets/images/integraciones/pagos/conekta-nodo-avanzado.png?fit=max\&auto=format\&n=3D3ye1Wdwh66cTgk\&q=85\&s=16ec102e31f28444899a076583a17241)
>
> Conekta node Advanced tab

> [tab] Outputs
>
> > [accordion] Successful payment
> >
> > Activates when Conekta confirms the transaction was approved.
> >
> > **Recommendations:**
> >
> > * confirm the order
> > * issue receipt or update status in external systems
>
> > [accordion] Pending payment
> >
> > Activates when the transaction is in process or requires later confirmation.
> >
> > **Recommendations:**
> >
> > * inform the user clearly
> > * avoid creating a second charge while the status is being resolved
> > * wait for event update when applicable
>
> > [accordion] Payment message sent
> >
> > Activates when the message with the payment button is sent successfully in the conversation.
> >
> > This output does **not** confirm payment. It only indicates the message with the payment button was sent successfully in the conversation.
> >
> > You can connect this output to a **post-payment-message support AI Agent** to assist the user while they decide to open checkout or if they have questions before paying.
> >
> > **Recommendations:**
> >
> > * resolve questions about how to open the payment button
> > * help if the WebView does not load or the user does not understand the step
> > * avoid creating a new charge without context
> > * do not confirm payments from this output
> >
> > **Example prompt (reference):**
> >
> > ```txt theme={null}
> > IMMEDIATE INTERRUPTION:
> > - If the user's last message contains the structure of a payment receipt (includes elements such as "Pago aprobado", "N° de operación", "Pagamento aprovado", "Operação", the ✅ symbol followed by transaction data, ━━━ separators, or patterns like "Monto:", "Valor:", "Medio de pago:", "Método:"), do NOT respond at all. Run end_function immediately with status "payment_completed".
> >
> >
> > You are "Payment Support", a help assistant for completing test payments inside WhatsApp. Context: the user just received a button (CTA) to make a test payment along with fictitious card data. Your role is NOT to sell or recalculate amounts: only help complete the payment or resolve button issues.
> >
> >
> > KEY BEHAVIOR
> >
> > - This agent can run even if the user has not written anything.
> > - If there is NO explicit question or problem from the user in the last message, send ONLY this proactive message (once) and then stay in reactive mode: "If you have any questions about your payment, message me here and I'll help."
> > - If the user DOES write (question/problem), respond directly, briefly, and clearly.
> > - Do not restart the process. Do not recalculate amounts. Do not generate new links. Do not invent information.
> > - Maximum 1 emoji per message.
> >
> > WHAT YOU SUPPORT
> > - How to pay from the button.
> > - Button does not open / loading error.
> > - Questions about test card data.
> > - Pending or rejected payment.
> > - Issues with the payment form.
> >
> > If the user reports a problem:
> > 1) Ask for a short description.
> > 2) If helpful, ask for a screenshot (they can send images).
> > 3) Suggest trying again or indicate the query can be escalated.
> >
> > DEMO CONTEXT
> > - The card data the user received is fictitious and safe; it does not generate real charges.
> > - The payment form opens from the CTA button they already received.
> > - This is a test environment to demonstrate how payments work in Brain Studio.
> >
> > CLOSING / END OF TASK
> > If the user says they already paid and do not need more help (e.g. "listo", "gracias", "ya pagué", "era eso", "todo bien"), reply briefly and close:
> >   Spanish: "Perfecto. Si necesitas algo más, aquí estaré."
> >   Portuguese: "Perfeito. Se precisar de algo mais, estarei por aqui."
> > Then run end_function with status "completed".
> >
> > ## TERMINATION
> >
> > Run end_function in these cases:
> > - WHEN: The message contains payment receipt structure (✅, ━━━, "Pago aprobado", "Pagamento aprovado", "N° de operación", "Operação") → status: "payment_completed", message: "" (empty, do not respond)
> > - WHEN: The user indicates they are done or do not need more help → status: "completed", message: "<farewell message>"
> >
> > ## Operational Rules
> >
> > - Always run end_function with this format:
> >   {
> >     "output_schema": "{\"status\": \"payment_completed|completed\", \"message\": \"...\"}"
> >   }
> > - For payment_completed: message MUST be an empty string "". Do not generate any response text before running end_function.
> > ```
>
> > [accordion] Failed payment
> >
> > Activates when the transaction was rejected, declined, denied, or not completed.
> >
> > **Recommendations:**
> >
> > * allow controlled retry
> > * offer support or an alternative path
>
> > [accordion] Error
> >
> > Activates on technical errors, provider errors, or communication failures during payment creation or processing.
> >
> > **Recommendations:**
> >
> > * log the error
> > * show contingency message
> > * retry in a controlled way and escalate if it persists

***

## How external confirmation works

When you select **External Confirmation Payment** in **Payment experience**, the node internally activates a conversational agent that guides the payer before generating the charge.

**1. The agent asks for the payer's details**

If the flow does not send **Cardholder first name**, **Cardholder last name**, or **Email**, the agent asks for them directly in the conversation, along with the **payment type**: approval in the **BBVA Wallet** app (the agent shows it as a "BBVA external redirect") or **unique SPEI code**.

The payer can reply with all the data together, in parts, or even in a voice note.

![WhatsApp conversation where the Conekta agent asks for name, last name, email, and payment type (BBVA redirect or SPEI code)](https://mintcdn.com/jelouai/1_JmEPMrIr40GNhs/assets/images/integraciones/pagos/conekta-confirmacion-externa-solicitud-datos.png?fit=max\&auto=format\&n=1_JmEPMrIr40GNhs\&q=85\&s=c9c27cb0cfaef439a1c75c63f9164987)

The agent asks for the missing details to generate the Conekta payment

**2. The agent confirms the details before continuing**

The agent shows a summary of the recorded details and asks the payer to reply **Confirm** to continue, or indicate what to correct.

![WhatsApp conversation with the payer data summary and the instruction to reply Confirm to continue](https://mintcdn.com/jelouai/1_JmEPMrIr40GNhs/assets/images/integraciones/pagos/conekta-confirmacion-externa-resumen-confirmacion.png?fit=max\&auto=format\&n=1_JmEPMrIr40GNhs\&q=85\&s=e80c300db3c138b3c93c9141e63fc98c)

Confirmation summary before generating the payment

**3. The payer completes the payment outside WhatsApp**

Depending on the chosen **payment type**:

* **BBVA Wallet approval:** the payer approves the payment in the **BBVA Wallet** app.
* **Unique SPEI code:** the agent delivers a code to paste in the payer's banking platform to complete the transfer.

<video controls preload="metadata" playsInline src="https://mintcdn.com/jelouai/1_JmEPMrIr40GNhs/assets/videos/integraciones/pagos/conekta/conekta-confirmacion-externa.mp4?fit=max&auto=format&n=1_JmEPMrIr40GNhs&q=85&s=065b150cbd5f67c380e3c87ac862807a">
  Your browser does not support video playback.
</video>

External confirmation with Conekta: BBVA Wallet approval

**4. Brain Studio continues the flow based on the result**

Conekta notifies the payment status via webhook and the node continues through the corresponding output (**Successful payment**, **Pending payment**, **Failed payment**, or **Error**), just like in the WebView experience.

> [!NOTE]
>
> With **External Confirmation Payment**, the payment is completed outside WhatsApp (in the BBVA Wallet app or on the payer's banking platform). The node does not open a WebView or capture card data inside the chat.

***

## Test payments in the test environment

If Conekta is connected with **test** credentials, you can test checkout with test data published by Conekta.

> [!NOTE]
>
> In the test environment, payment is fictitious and does not move real money.

**1. Confirm test credentials**

Verify Conekta is installed with test environment credentials.

**2. Configure the node in the test environment**

In the **Advanced** tab, verify the environment corresponds to development/test and confirm the **Payment experience** you want to test (**WebView Payment** or **External Confirmation Payment**).

**3. Test from WhatsApp**

Trigger the flow from WhatsApp.

* With **WebView Payment**, open the Conekta checkout and select a test payment method.
* With **External Confirmation Payment**, complete the details the agent asks for and follow the **BBVA Wallet approval** or **SPEI code** flow.

**4. Validate flow output**

Verify which output the flow continues through:

* **Successful payment**
* **Pending payment**
* **Failed payment**
* **Error**

***

## Go live

If you installed Conekta with **development/test** credentials, you can start going live from the **Advanced** tab of the Conekta node in **Canvas** or from the **Conekta** page in **Marketplace**.

In both cases the same modal opens to enter production credentials and confirm the corresponding configuration.

Before operating with real payments:

* Make sure you have complete **production** credentials: public key and private key.
* Use the **Go live** flow described in [Connect in Brain Studio](https://docs.jelou.ai/en/guides/integrations/payments/providers/conekta/connect-in-brain-studio.md).
* Replace any test data in the node with real flow data.
* Run a low-amount real test before scaling.

***

## Important considerations

> [accordion] Environment depends on installation
>
> If you installed Conekta with test credentials, test with test data. If you installed with production credentials, use real data.

> [accordion] Avoid duplicate payments
>
> In pending or failed scenarios, inform clearly before starting another collection attempt. Keep retries controlled.

> [accordion] External confirmation happens outside WhatsApp
>
> With **External Confirmation Payment**, the payment does not happen inside WhatsApp. Your flow must handle **Pending payment** and the final outputs without assuming immediate confirmation, just like with other external confirmation providers.

> [accordion] Test data does not work in production
>
> Test cards and methods only apply in the test environment. In production the user must use real data.

***

## Next step

> [card] [Coverage and pricing](https://docs.jelou.ai/en/guides/integrations/payments/providers/conekta/coverage-and-pricing.md)
>
> Review Conekta availability, currency, payment methods, and commercial considerations.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.