Usage and configuration

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.

If you have not installed the integration yet, follow Connect in Brain Studio first.

Add the node to Canvas

Open your flow in Canvas

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

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.

Connect the node at the collection point

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

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 — Conekta node in Canvas with the side panel open on Payment data

Configure the node

Inputs
Outputs

Payment data

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.

Header

string

Title of the payment button message.Shown when Customization is enabled. Appears in the message preview.

Content

string

Main text of the payment button message.Shown when Customization is enabled. Appears in the message preview.

Footer

string

Closing text of the payment button message.Shown when Customization is enabled. Appears in the message preview.

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}}.

Taxable amount

number

required

Amount subject to VAT. Numbers only.You can map it from flow variables.

Tax-free amount

number

required

Tax-exempt amount. If not applicable, use 0. Numbers only.You can map it from flow variables.

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.

Cardholder last name

string

Last name of the person holding the payment.Applies when Payment experience is External Confirmation Payment.

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.

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 — 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 — Payment data with the External Confirmation Payment experience: Cardholder first name, Cardholder last name, Document or tax ID number, and Email fields

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

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.

The environment depends on installed credentials. Do not go live without preparing production credentials.

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 — Payment experience field on the Conekta node's Advanced tab

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.

Currency

string

required

Defines the collection currency.For Conekta Mexico, you will normally use MXN.

VAT percentage

number

Defines the VAT percentage applied to the collection operation.

Payment metadata

string

Optional field to store internal reference such as order ID, sequence number, user ID, or booking ID.

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}}.

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 — Conekta node Advanced tab

Successful payment

Activates when Conekta confirms the transaction was approved.Recommendations:

confirm the order
issue receipt or update status in external systems

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

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):

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.

Failed payment

Activates when the transaction was rejected, declined, denied, or not completed.Recommendations:

allow controlled retry
offer support or an alternative path

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.

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) — The agent asks for the missing details to generate the Conekta payment

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 — Confirmation summary before generating the payment

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.

External confirmation with Conekta: BBVA Wallet approval

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.

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.

In the test environment, payment is fictitious and does not move real money.

Confirm test credentials

Verify Conekta is installed with test environment credentials.

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).

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.

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.
Replace any test data in the node with real flow data.
Run a low-amount real test before scaling.

Important considerations

Environment depends on installation

If you installed Conekta with test credentials, test with test data. If you installed with production credentials, use real data.

Avoid duplicate payments

In pending or failed scenarios, inform clearly before starting another collection attempt. Keep retries controlled.

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.

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

Coverage and pricing

Review Conekta availability, currency, payment methods, and commercial considerations.

Getting Started

Developer

Jelou CLI

Outbound Messaging

Inbox

Marketplace

Channels

Configuration

Billing

Add the node to Canvas

Configure the node

Payment data

Advanced

How external confirmation works

Test payments in the test environment

Go live

Important considerations

Next step

Coverage and pricing

​Add the node to Canvas

​Configure the node

​Payment data

​Advanced

​How external confirmation works

​Test payments in the test environment

​Go live

​Important considerations

​Next step

Coverage and pricing

Add the node to Canvas

Configure the node

Payment data

Advanced

How external confirmation works

Test payments in the test environment

Go live

Important considerations

Next step