Skip to main content

​
Payments with SumUp, Mercado Pago, Flow and Wompi

With the Payment Action, your ChatNorris agent charges within the conversation. You set up a closed catalog of items with their amounts, and the agent:
  • builds a cart with one or more items from the catalog, with the total;
  • asks the visitor for explicit confirmation before charging;
  • generates a payment link for the total with the provider you choose;
  • lets the visitor know in the chat when the provider confirms the payment.
The agent never makes up an amount: it can only charge the exact amounts you configure. Charges are processed in your own provider account. It works in the web widget, WhatsApp, Instagram, Messenger, Telegram, Email, and the API.

​
Requirements

  • A ChatNorris account on the Standard or Premium plan. You can see the plans at chatnorris.ai/pricing.
  • At least one agent created in ChatNorris. If you don’t have one yet, follow Create an agent.
  • An account with at least one of the providers (SumUp, Mercado Pago, Flow, or Wompi) and access to its API credentials.
  • Owner or Admin role in your ChatNorris organization.

​
Connect a provider

Connect at least one provider on the agent. You can connect several and choose in the Action which one is used to charge.
1

Open the agent's Integrations hub

In ChatNorris, go to My agents → [your agent] → Integrations and choose SumUp, Mercado Pago, Flow, or Wompi.
2

Paste the credentials and connect

Each provider asks for different details: you’ll find them below, in each one’s section. Click Connect.
3

Test the connection

Use Test connection to confirm the credentials work before using them in the Action.
The hub only shows the last 4 characters of each key. If you rotate it at the provider, use Replace key in the row’s ··· menu: the connection stays the same and the Action isn’t touched.

​
SumUp

It asks for the Merchant code (you can see it in the SumUp dashboard, for example MH4H92C7) and the API key, which you generate at me.sumup.com/settings/api-keys. The visitor pays on SumUp’s payment page (Hosted Checkout).

​
Mercado Pago

It asks for the Public Key and the Access Token, which you find in your Mercado Pago account, under Tus integraciones → Credenciales (they start with APP_USR-). The visitor pays on Mercado Pago’s page (Checkout Pro). A single connection works for all of Latin America. The link expires after 30 minutes; if it expires, the visitor can ask for a new one.

​
Flow (Chile)

It asks for your Flow account’s API Key and Secret Key, which you find in Flow → Mis datos, Integraciones tab. ChatNorris validates them with Flow when saving and detects whether they’re test (sandbox) or production keys: production and sandbox are separate accounts, with separate keys. With sandbox keys, the connection shows the Sandbox label and payments are test payments, with no real money. If you choose Flow as the gateway in the Action:
  • Items have to be in Chilean pesos (CLP), with whole amounts of at least 350 CLP (Flow’s minimum). If any enabled item doesn’t meet these rules, the Action asks you to fix it or disable it before turning it on.
  • Before generating the link, the agent asks for the visitor’s email if it doesn’t have it yet: Flow requires it to send them the receipt. If Flow rejects that email, the agent asks for another one.
  • The visitor pays on Flow’s page with Webpay (credit, debit, and prepaid), Khipu (transfer), or the other methods you have enabled in your Flow account.
  • The link expires after 30 minutes; if it expires, the visitor can ask for a new one.

​
Wompi (Colombia)

For now it works with Wompi Colombia accounts. It asks for four details that you find in your Wompi dashboard, under Desarrolladores (“Llaves del API” and “Secretos para integración técnica”): All four have to be from the same environment. With test keys (pub_test_…, prv_test_…, test_integrity_…, and test_events_…), the connection shows the Sandbox label and payments are simulated, with no real money. If a key doesn’t work, the form tells you which one. To update the connection, paste all four again.
After you connect, ChatNorris shows you the Events URL. Copy it into Wompi → Desarrolladores → URL de Eventos, in the same environment as your keys, so payments are confirmed even if the visitor closes the payment tab. Wompi allows only one events URL per environment, so it replaces whichever one you had set there: if another system was using it (for example, your online store), it stops receiving those notifications.
If you choose Wompi as the gateway in the Action:
  • Items have to be in Colombian pesos (COP), with whole amounts of at least 1,500 COP. The multi-item cart works the same as with the other providers.
  • The visitor pays on Wompi’s page with card, Nequi, Daviplata, PSE, Transferencia Bancolombia, or SU+ Pay, depending on the methods you have enabled in your Wompi account.
  • The link expires after 30 minutes; if it expires, the visitor can ask for a new one.

​
Configure the Action

Connecting the provider doesn’t turn anything on yet. For the agent to charge:
1

Create the Payment Action

Go to My agents → [your agent] → Actions, click New action, and choose Payment.
2

Choose the payment gateway

The Payment gateway field decides which connected provider generates the link. Changing it doesn’t delete the item catalog or the connections: it only decides which one is used.
3

Set up the item catalog

In Item catalog, add each chargeable item with Add item: name, description (optional), amount, and currency. The currency is per item; the Action’s Currency field only sets the default currency for new items. The agent can only charge the exact amounts configured here.
4

Customize the success message and the return page

The Message after payment is sent in the chat when the provider confirms the charge. The Return page (optional) is where the visitor goes back to after paying; if left empty, they see the provider’s own success screen.
5

Turn on the Action and save

With Action enabled on, click Save. While it’s disabled, the agent never offers or generates payment links.
In When to use this action, you can adjust the instructions the agent follows, turn by turn, to decide whether it should generate a payment link. With Restore default text you go back to the original text.
We recommend using Claude Sonnet or a higher model as the main model on agents with this action (Settings → AI). Creating a payment link is a real charge. In tests, cheaper models (for example, Haiku) sometimes confirm a payment or make up a receipt number without having generated any checkout, even with explicit instructions not to. The Action’s form shows this notice with a link to the AI settings.
The agent always asks the visitor for explicit confirmation before generating the payment link: this can’t be turned off. See which replies count as confirmation in Agent actions.Charges are processed in your own SumUp, Mercado Pago, Flow, or Wompi account: ChatNorris never receives the money or sees card details. It only generates the link and learns about the confirmation, which it always verifies with the provider before letting the visitor know.
An agent builds purchases from a single source. If it already has the Build a purchase capability of a connected store turned on (for example, Jumpseller or Odoo), turn it off before enabling the Payment Action, and vice versa.

​
Import items from a CSV

If you have many items, use Import CSV in the catalog. The file’s first row must have the headers; columns are recognized in any order: Before importing, you see how many items were detected and how many rows were skipped: a row without a name or without a valid amount is discarded; a price is never made up. Imported items are added to the ones you already had. The catalog holds up to 50 items.

​
Cart: several items in one charge

The visitor can build a cart with several catalog items in the same conversation: add, change quantities, and remove items, even several changes in a single message (“add one of 60 and remove one of 45”). The agent shows them the cart with the total and, when the visitor explicitly confirms they want to pay, generates a single payment link for the total.
  • Prices always come from the Action’s catalog and are revalidated on every turn. If a price changed, the agent asks again for confirmation of the new total.
  • A cart never mixes currencies.
  • If the visitor changes the cart in the same message in which they ask to pay, the agent doesn’t generate the link: it first asks them to confirm the new total.
  • When the payment is confirmed, the cart is closed. If the visitor asks again for the link for the same cart, the agent reuses the one that’s still valid.
  • In the Playground, a real payment link is never created.
Every change to the cart and the payment is recorded in the conversation as an internal note, which only your team sees.

​
How the visitor sees it by channel

  • Web widget: the cart appears as a Your cart card with each line (quantity × item and subtotal), the Total, and a Pay button with the amount that opens the payment page. If the cart changes, only the most recent card keeps the button.
  • Telegram and WhatsApp: the payment link arrives as a Pay button below the message, instead of the URL pasted at the end of the text. If sending with a button fails, the agent sends the same message with the link in the text.
  • Other channels: the link goes in the message text.

​
After the payment

  • Conversation resolved: if a conversation with a confirmed payment closes due to inactivity and the visitor didn’t write again after paying, it moves to Resolved. The change is applied once a day, so it may show as closed for a few hours.
  • Where to see payments: in the conversation’s Details, the Payments section appears (only if the conversation has confirmed payments). In Leads, you have the Payment column, the Paid filter, and the Payments section in each lead’s panel. See Conversations and Leads.

​
Disconnect

In My agents → [your agent] → Integrations → [provider], click Disconnect (it’s also in the row’s ··· menu). The Payment Action that uses that connection is disabled, but it keeps its configuration and the item catalog isn’t deleted. The key is deleted from ChatNorris. To charge again, connect the provider again and re-enable the Action. If you only want to stop charges for a while, turn off the integration’s Active toggle: the credentials are kept and the Action can’t generate links until you reactivate it. Deleting the Payment Action doesn’t delete the connection or the history of charges already made.

​
Frequently asked questions

No. Charges are processed in your own SumUp, Mercado Pago, Flow, or Wompi account. ChatNorris doesn’t receive the money or see card details: it only generates the payment link and learns about the confirmation.
Yes. You can connect more than one in Integrations; the Action’s Payment gateway field decides which one generates the link. Each provider allows only one connection per agent.
Check the catalog’s enabled items: with Flow, they have to be in CLP, with whole amounts of at least 350 CLP; with Wompi, in COP, with whole amounts of at least 1,500 COP. Fix or disable the ones that don’t comply.
Check that you pasted the connection’s Events URL into Wompi → Desarrolladores → URL de Eventos, in the same environment as your keys. Without it, the payment isn’t confirmed if the visitor closes the payment tab.
In the Playground, a real payment link is never created. With Flow and Wompi, you can also connect sandbox keys: the connection shows the Sandbox label and payments are test payments.
No. Connecting and testing the integration doesn’t cost credits. See AI models and credits.