Automation · Collections and receivables

Get paid on WhatsApp with a SumUp payment link

An AI agent creates the charge for what the customer ordered in SumUp, sends the payment link on WhatsApp and checks in SumUp whether they paid.

Show me this with my own operation See every automation

How do I charge a customer on WhatsApp with SumUp without opening the dashboard to create the link?

A Met connected to SumUp identifies your merchant, checks which payment methods it can offer and creates a checkout with the amount, the currency and the order reference. With the payment page hosted by SumUp turned on for that checkout, it sends the customer the link in the same WhatsApp conversation. The customer pays on SumUp's page and their card details never go through the chat. When they say they paid, the Met checks the checkout and the transaction in SumUp and replies with the real status; if the customer asks, it summarizes the receipt.

What starts it

When the customer writes

It starts when the customer decides to buy inside the WhatsApp conversation. There is no trigger to configure: the Met assigned to the line creates the charge and sends the link right there.

Nothing to set up. The Met assigned to that channel picks up the conversation and runs the procedure inside it.

Who runs it

Sales Met that closes in the chat

Sales team

It is the Met that carries the conversation to the purchase. Its work ends when the customer has a correct payment link and the Met can say, with what SumUp reports, whether the payment came in.

Run by the sales closing Met

Channels: WhatsApp

What you need connected

SumUp Collect and manage

5 steps · 7 tools

The procedure, step by step

Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.

1
Identify the merchant that charges

The Met lists the merchants the connected account belongs to and keeps the merchant code you charge with. If the account has more than one, the skill tells it which one to use so it does not charge with the wrong merchant.
- list_memberships SumUp
- get_merchant SumUp
2
Check the available payment methods

Before promising a payment method, the Met checks which ones your merchant can offer in a checkout. That way it does not tell the customer they can pay with something your account lacks.
- get_payment_methods SumUp
3
Create the checkout and send the link

The Met creates the checkout with the agreed amount, the currency and the order reference, with the payment page hosted by SumUp turned on. SumUp returns that page's link and the Met sends it to the customer on WhatsApp. Creating the checkout charges nothing yet.
- create_checkout SumUp
4
Confirm whether the payment came in

When the customer writes that they paid, the Met looks up the checkout and checks the transaction linked to it. It replies with the status SumUp returns; if the payment does not show up, it tells the customer instead of taking it for granted.
- get_checkout SumUp
- get_transaction_v2_1 SumUp
5
Summarize the receipt if asked

If the customer needs proof of payment for their bookkeeping, the Met pulls the transaction's receipt details and summarizes them in the conversation.
- get_receipt SumUp

Before you start

What you need ready

The Met solves none of these for you. If one is missing, the automation stops there.

SumUp connected with checkout creation on

The admin creates an OAuth app in SumUp with the return URL Met shows. Then, in Met, open Connections → SumUp → Connect, paste the client ID, authorize and leave checkout creation on.
A SumUp merchant account that takes online payments

The SumUp account you sell with. SumUp recommends testing the flow with a test (sandbox) merchant account before charging for real.
A WhatsApp line with the Met assigned

The business connects its WhatsApp Business API line and assigns the sales Met. The link is sent inside that conversation.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

It does not work out the price: it charges the amount your catalog or skill states. If the price is wrong there, the link goes out with the wrong price.
It does not refund in this procedure. refund_transaction starts turned off and the procedure does not use it; a refund is your team's decision.
It does not ask for confirmation in the chat before creating the checkout: if the action is on, it creates it. The admin decides which writes stay on.
It does not see the customer's card details. Payment happens on SumUp's page and the Met only reads the result.
It does not ship the order. Once the payment comes in, delivering the product is still the job of your store or another integration.

FAQ

Questions about this automation

No. They get a link to the payment page hosted by SumUp and pay there, with the methods your merchant offers. Then they come back to the chat and the Met confirms the payment.

The Met does not trust the conversation: it checks the checkout and the transaction in SumUp. If SumUp does not show the payment, the Met tells the customer.

Yes. SumUp recommends connecting a test (sandbox) merchant account before testing payment flows, and the procedure works the same with it.

You do, with your SumUp account's rates. Meteor does not charge for the calls your Met makes to SumUp and does not resell the service.

Keep going