Usage and configuration

Once the integration is connected, the Mercado Pago node is available in Canvas and lets you create embedded WebView checkout experiences within the conversational flow.

First time implementing a payment? Start with the Tutorial: your first payment.If you have not installed the integration yet, begin with Connect in Brain Studio.

Add the node to Canvas

Open your flow in Canvas

In Brain Studio, open the flow where you want to add Mercado Pago payments.

Add the Mercado Pago node

Add Mercado Pago from the Canvas toolbar, under 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 payment step

Connect the Mercado Pago node after the flow already has the amount, buyer data, and purchase confirmation.

Open the configuration panel

Select the node to open the right-side panel. Complete the Payment data and Advanced tabs, and review the available outputs on the Canvas node.If required fields are missing, the node shows Incomplete configuration. Check the node fields. and the environment badge (Development or Production).

Configure the node

Payment data
Advanced

Mercado Pago node in Canvas with the Payment data tab open in the side panel — Payment data tab: personalization, amounts, and buyer email

Personalization

boolean

default:"false"

Turn it on to define the messages that accompany your payment button.When enabled, it shows the Header, Body, and Footer fields.

Example message with customized text and Mercado Pago payment button in WhatsApp — Example of a customized payment button message in WhatsApp

Header

string

Title of the payment button message.Shown when Personalization is enabled.

Body

string

Main text of the payment button message.Shown when Personalization is enabled.

Footer

string

Closing text of the payment button message.Shown when Personalization is enabled.

Payment reason

string

required

Descriptive text for the charge. Examples: order number, product, service, or internal reference.

Taxable amount

number

required

Amount subject to VAT or other configured tax. Numbers only.

Tax-free amount

number

required

Tax-exempt amount. Numbers only. If it does not apply, use 0.

Buyer email

string

required

Email the buyer will use at checkout.In Development, it must be a Mercado Pago test user email for the corresponding country.In Production, use the buyer’s real email captured in the flow.

If the integration is in Development, copy one of these test emails into Buyer email. It must be from the same country as your test credentials.

🇨🇱 Chile

[email protected]

🇵🇪 Peru

[email protected]

🇨🇴 Colombia

[email protected]

🇲🇽 Mexico

[email protected]

🇧🇷 Brazil

[email protected]

🇦🇷 Argentina

[email protected]

🇺🇾 Uruguay

[email protected]

Environment

Shows whether Mercado Pago operates in Development or Production.In Development, you will see Your integration is in development mode. Move it to production when you are ready. and you can start the Go to production flow.In Production, the selector reflects that the integration already operates with production credentials.

Development corresponds to an installation with Mercado Pago test credentials. Production corresponds to production credentials.

Do not go to production without a Production credentials Access Token ready in Mercado Pago.

Payment button expiration

string

Defines how long the payment button remains valid after it is sent.Select an option from the list available in Brain Studio.

Currency

string

required

Defines the charge currency (for example, CLP).It must match the country of the connected credentials and the Charge currency set when installing the integration in Connect in Brain Studio.

VAT percentage

number

Defines the VAT percentage applied to the charge.It should be consistent with the Applied VAT configured when installing the integration.

Payment metadata

string

Optional field for internal reference such as order ID, sequence number, or user ID.

Save response

string

Stores the selected option in a memory variable.Enter the variable name after the {{$memory.}} prefix. Maximum 50 characters.The response will be stored in memory and available in later nodes.

Useful for traceability, later validations, or flow decisions.

Node outputs

Outputs appear on the Mercado Pago node in Canvas. Connect them according to the result you want to handle in your flow.

Successful payment

Triggers when Mercado Pago confirms the transaction was approved.Recommendations:

confirm the order
send a receipt or notification
update purchase status in your systems

Pending payment

Triggers 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 a webhook update or later query when applicable

Payment message sent

Triggers when the message with the payment button is sent successfully in the conversation.This output does not confirm payment. It only indicates that 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:

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

Act as “Payment Support”, a brief assistant to help the user after receiving a payment button message inside WhatsApp.

Context:
The user just received a message with a payment button to open a WebView checkout. Your role is to answer simple questions before the user completes payment.

────────────────────
IMMEDIATE INTERRUPTION
────────────────────
If the last message or event received contains payment result signals, DO NOT respond.

Payment result signals:
- successful payment, approved payment, completed payment
- pending payment
- failed payment, rejected, declined, or denied
- payment error
- automatic provider confirmation
- receipt, proof, operation number, transaction ID, payment ID
- messages with receipt structure, amounts, payment method, or final status

When you detect any of these signals, stop immediately. Payment results must be handled by the official payment node outputs, not by this agent.

────────────────────
BEHAVIOR
────────────────────
- If the user did not ask a question or report a problem, do not respond.
- If the user has a question, respond briefly, clearly, and helpfully.
- Do not confirm payments.
- Do not invent payment statuses.
- Do not recalculate amounts.
- Do not promise reversals, approvals, refunds, or settlement times.
- Do not generate new links or new charges.
- If the user needs human help, indicate they can wait for support or continue through the channel defined by the flow.

────────────────────
WHAT YOU CAN ANSWER
────────────────────
You can help with:
- how to open the payment button
- what to do if the WebView does not load
- what to do if the user closed checkout
- basic questions about completing the payment form
- general guidance if payment appears pending or rejected, without confirming status

────────────────────
SUGGESTED RESPONSES
────────────────────
If the user asks how to pay:
“Open the payment button and follow the checkout instructions. When you finish, come back to this conversation.”

If the WebView does not load:
“Try opening the button again and check your connection. If the problem continues, try again later or ask for help in this chat.”

If the user says payment was rejected:
“You can review the entered data and try again. If the problem continues, use another payment method or request help through this channel.”

If the user says they already paid:
Do not confirm payment. Do not respond if the message looks like an automatic result or receipt. If it is only a user phrase, respond:
“Thanks. Let’s wait for payment confirmation to continue.”

────────────────────
CLOSING
────────────────────
If the user says they no longer need help, respond briefly:
“Perfect. If you need anything else, I’ll be here.”

Failed payment

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

allow a controlled retry
offer a support path or an alternative route

Error

Triggers on technical errors, provider errors, or communication failures during payment creation or processing.Recommendations:

log the error
show a contingency message
retry in a controlled way and escalate if it persists

Test payments

If Mercado Pago is connected with test credentials, checkout must be completed with a Mercado Pago test user.

In test mode, payment is fictitious and does not move real money. The Development environment in the node corresponds to Mercado Pago test credentials.

Confirm test credentials

Verify that Mercado Pago is installed with a Test credentials Access Token.

Configure the node in test environment

In the Advanced tab, verify the environment is Development.

Use a test user email

In Buyer email, use a test user from the same country as the connected credentials.The full list by country is in the first payment tutorial.

Test from WhatsApp

Trigger the flow from WhatsApp, open the Mercado Pago WebView checkout, and complete payment with the test cards by country for the corresponding country.

Validate flow output

Verify which output the flow continues through:

Payment message sent (button send only)
Successful payment
Pending payment
Failed payment
Error

Go to production

If you installed Mercado Pago with test credentials, you can start going to production from the Advanced tab of the Mercado Pago node in Canvas or from the Mercado Pago page in Marketplace. In both cases, the same modal opens to enter the production Access Token and confirm the configuration. Before operating with real payments:

Make sure you have a Production credentials Access Token in Mercado Pago.
Use the Go to production flow described in Connect in Brain Studio.
Confirm that Currency and VAT percentage in the node match the production configuration.
Replace any test data in the node with real flow data.
In production, use the buyer’s real email.
Run a low-amount real test before scaling.

Important considerations

Environment depends on installation

If you installed Mercado Pago with test credentials, use test users and test emails. If you installed with production credentials, use the buyer’s real data.

Buyer email is critical in Development

In testing, Buyer email must belong to a Mercado Pago test user for the corresponding country.If you use a real email in Development, checkout may fail or not continue through the expected output.

Currency and VAT must be consistent

The node’s Currency and VAT percentage must match what was set when installing the integration and the country of your Mercado Pago credentials.

Avoid duplicate payments

In pending or failed scenarios, inform the user clearly before starting a new charge attempt. Keep retries controlled.

Payment methods and pending statuses

Some Mercado Pago payment methods may remain pending before settlement. Your flow must handle Pending payment without assuming the charge is already confirmed.

Embedded WebView in WhatsApp

For checkout to open inside WhatsApp, the account must be a verified WhatsApp Business account. If it is not verified, checkout will open in the device’s external browser. See the warning in Connect in Brain Studio.

Next step

Coverage and pricing

Review availability by country, payment methods, and Mercado Pago reference fees.

Getting Started

Developer

Jelou CLI

Outbound Messaging

Management

Marketplace

Channels

Configuration

Billing

Add the node to Canvas

Configure the node

Node outputs

Test payments

Go to production

Important considerations

Next step

Coverage and pricing

​Add the node to Canvas

​Configure the node

​Node outputs

​Test payments

​Go to production

​Important considerations

​Next step

Coverage and pricing

Add the node to Canvas

Configure the node

Node outputs

Test payments

Go to production

Important considerations

Next step