Automation · Collections and receivables

Confirm on WhatsApp whether a customer's payment came in through Fintoc

An AI agent checks in Fintoc whether the payment the customer says they made already came in, and replies on WhatsApp with the real status.

Show me this with my own operation See every automation

How do I confirm to a customer on WhatsApp that their Fintoc payment came in, without opening the dashboard?

A Met connected to Fintoc finds the operation that lists payment intents, reads which parameters it needs and queries it with the amount and date the customer gives. With the payment found, it pulls its details and replies on WhatsApp with the status that payment has in Fintoc, not with what the customer believes. If the customer paid twice and the admin turned writing on, the Met creates the refund of the duplicate payment; if writing is still off, which is how it starts, it hands the case to your team.

What starts it

When the customer writes

It starts when a customer writes on WhatsApp that they paid and asks whether the payment arrived. There is no trigger to configure: the Met assigned to the line runs the procedure inside that conversation.

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

Who runs it

Support Met that confirms payments

Customer service team

This is not a named, seeded Met. It is the Met that already answers the business's WhatsApp, with Fintoc connected. Its work ends when the customer knows, with Fintoc's data, whether their payment came in, or when a duplicate payment is refunded or in the team's hands.

Run by the customer support Met

Channels: WhatsApp

What you need connected

Fintoc Collect and manage

5 steps · 5 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
Find the payments operation

The Met searches Fintoc's operations for the one that lists payment intents. Fintoc has no tool per action: first the operation is found, then it is run.
- fintoc_tool_search Fintoc
2
Read what the operation needs

Before querying, the Met pulls the operation's parameters and permissions. That tells it which fields it can filter on and whether the session has the required scope, instead of guessing.
- fintoc_tool_details Fintoc
3
Look up the customer's payment

The Met queries payment intents with the amount and date the customer gave. If several similar ones show up, it asks the customer for one more detail before answering about the wrong one.
- fintoc_tool_read Fintoc
4
Check the payment and reply

With the payment identified, the Met pulls its details by id and replies to the customer with the status it has in Fintoc. If the payment does not show up, it says so plainly and asks for the receipt.
- fetch_resource Fintoc
5
Refund a duplicate payment, if allowed

If the customer paid the same thing twice and the admin turned on fintoc_tool_write, the Met creates the refund of the duplicate payment. If writing is still off, it refunds nothing: it logs the case for your team to resolve.
- fintoc_tool_write Fintoc

Before you start

What you need ready

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

Fintoc connected in live mode

In Met, open Connections → Fintoc → Connect and authorize on Fintoc's consent screen with the payments scopes. Fintoc requires an active account with live mode access.
Writing, only if you will refund payments

fintoc_tool_write starts turned off. If you want the Met to create refunds, the admin turns it on, knowing it enables every supported write and not just that one.
A WhatsApp line with the Met assigned

The business connects its WhatsApp Business API line and assigns the Met that answers customers. The answer happens inside that conversation.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

It does not charge: it creates no payment links or sessions. Fintoc lists checkout sessions over MCP but does not create them, so the charge is set up another way.
It does not guess the payment. If the customer gives no amount or date, or there are several identical payments, the Met asks before answering.
It does not ask for confirmation in the chat before creating a refund: if writing is on, it creates it. That is why it starts turned off and the admin decides.
It does not cancel subscriptions or pay invoices. Fintoc does not expose those actions over MCP; the Met hands the case to your team.
It does not work with test data. The token operates only in live mode: what it reads and writes belongs to your real account.

FAQ

Questions about this automation

It can, if the question is ambiguous. That is why it searches by amount and date and, if it finds several similar payments, asks the customer for one more detail before answering.

The procedure works the same up to confirming the payment. Only the last step changes: instead of refunding a duplicate payment, the Met leaves the case for your team.

Fintoc's page says refunds can be listed, created and cancelled over MCP, without more detail. The Met reads the operation's parameters before running it.

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

Keep going