Integration · Collect and manage

SumUp and Meteor AI agents

Connect SumUp to a WhatsApp Met: create the payment link, check whether the customer paid and look up transactions, receipts and payouts.

Book a demo See every integration

How do I get paid on WhatsApp with SumUp without opening the dashboard?

With the SumUp ready connector, your Met uses SumUp's official MCP server on your merchant account. On WhatsApp it creates a checkout with the amount and currency you agreed and, with the payment page hosted by SumUp, sends the customer the link to pay. When the customer says they already paid, the Met checks the checkout and the transaction in SumUp and replies with the real status, and it can pull the receipt details. It also looks up transaction history, payouts to your account and the status of your card readers. Refunds start turned off until the admin turns them on. Usage runs on your SumUp account.

What it automates

What a Meteor Met does with SumUp

Get paid with a link inside the chat

The customer confirms the order. Your Met creates a checkout with the amount, the currency and an order reference, requests the payment page hosted by SumUp and sends the link on WhatsApp. Card details are typed on SumUp's page, not in the chat.

Answer whether the payment came in

When the customer says they paid, the Met looks up the checkout by the order reference and checks the transaction in SumUp. It replies with the status SumUp returns, not with what the customer believes.

Send the receipt details

With the transaction found, the Met pulls the receipt details and summarizes them for the customer who needs them for their bookkeeping.

Charge at the counter from the team chat

If you serve customers with a SumUp card reader, the Met checks that the reader is connected and sends it the charge, and stops it if the customer changes their mind before paying.

24 tools

Everything your Met can ask SumUp for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`list_memberships`	Lists the merchants the authorizing user belongs to, to know which one to charge with.
`get_merchant`	Returns a SumUp merchant's details from its merchant code.
`get_payment_methods`	Lists the payment methods the merchant can offer in a checkout.
`create_checkout`	Creates a checkout with an amount, a currency and your own reference. With the payment page hosted by SumUp turned on, it returns the link for the customer to pay. Creating it charges nothing.
`get_checkout`	Returns a checkout to confirm the status the payment ended in.
`list_checkouts`	Lists the created checkouts that have a given reference.
`update_checkout`	Changes the details of a checkout already created, such as its reference or its expiry.
`deactivate_checkout`	Deactivates an unprocessed checkout so it can no longer be paid. Starts turned off.
`list_transactions_v2_1`	Lists the merchant's transaction history.
`get_transaction_v2_1`	Returns the full details of a transaction by its ID or code.
`get_receipt`	Returns the receipt details of a transaction.
`refund_transaction`	Refunds a transaction, in full or in part. Starts turned off.
`list_payouts_v1`	Lists the merchant's payouts and payout deductions in a date range.
`create_customer`	Creates a saved customer that payment methods can later be attached to.
`get_customer`	Returns a saved customer by ID.
`update_customer`	Updates a saved customer's personal details.
`list_payment_instruments`	Lists a customer's saved payment methods.
`deactivate_payment_instrument`	Deactivates a customer's saved card. Starts turned off.
`list_readers`	Lists the merchant's card readers.
`get_reader`	Returns a card reader's details.
`get_reader_status`	Returns a reader's last known status, such as the screen it shows during a payment.
`create_reader_checkout`	Sends a charge to a card reader. It is asynchronous: the transaction can take a while to show up on the device.
`get_reader_checkout`	Returns the charge that was sent to a reader.
`create_reader_terminate`	Stops the charge in progress on a reader.

The limits

What the SumUp integration does NOT do

We would rather say it here than have you find out during rollout.

It does not refund until the admin allows it. refund_transaction starts turned off, as do deactivating a checkout or a saved card. Once on, the Met does not ask you for confirmation in the chat: the control is which actions the admin leaves on.
It does not see the customer's card details. Payment happens on SumUp's page or on the reader; the Met only reads the result.
It does not manage your merchant account. This page leaves out the member, role and person tools, and the ones to register, edit or delete readers.
It does not accept a SumUp API key. The hosted server only works with the OAuth authorization you grant when connecting; sup_sk_ keys are for the local server.
It does not pay SumUp's fees. Each charge pays your SumUp account's rates, and Meteor does not resell the service.

Before you start

What you need to connect SumUp

1

A SumUp merchant account

The SumUp account you get paid with. SumUp recommends testing payment flows with a test (sandbox) merchant account before charging for real.
2

An OAuth app in SumUp with Met's return URL

SumUp does not register clients automatically, so the admin creates an OAuth app in the SumUp developer dashboard, registers the return URL Met shows and copies that app's client ID.
3

Connect it in Met

In Met, open Connections → SumUp → Connect, paste the client ID and sign in to SumUp to authorize access.
4

Decide which actions stay on

The workspace admin chooses which actions stay on. Refunds and deactivating checkouts or saved cards start turned off.

Frequently asked questions

Questions about SumUp and Meteor

It sends a link. It creates the checkout in SumUp and shares the payment page hosted by SumUp with the customer, who pays with the methods your account offers.

The ones SumUp's checkout accepts, including Colombian pesos, Chilean pesos, Brazilian reais and US dollars, depending on what your merchant account allows.

Only if the admin turns on refund_transaction, which starts turned off. With the action on, the refund can be full or partial.

Because SumUp does not offer automatic OAuth client registration. That is why your admin creates the app in SumUp, with Met's return URL, and Met uses its client ID.

You do, with your SumUp account and its per transaction fees. Meteor does not charge for the calls your Met makes to SumUp.

Step by step