Mangopay

Run marketplace payment operations on Mangopay. Agents onboard natural users, create and inspect e-money wallets, move funds between wallets with configurable platform fees, and confirm card or bank-transfer pay-ins have settled before releasing goods.

8 actions OAuth available

Mangopay website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A marketplace sale completes and the buyer's payment enters processing

Get PayIn polls the pay-in until its status resolves: SUCCEEDED or FAILED

The agent confirms credited funds match the sale amount before anything else moves

Get Wallet verifies the buyer-side wallet balance actually holds the settled funds

For transfers above the platform's threshold, the finance owner reviews the split, seller amount and platform fee, before funds move

Create Transfer moves the seller's share to their wallet, with the fee credited to the platform's fees wallet

The finance channel receives the settlement summary with pay-in ID, transfer ID, and amounts in the audit log

What This Integration Enables

Marketplace payments have a structural property that simple checkout flows do not: the money moves twice. Once inward, from the buyer's card or bank to a wallet, and once sideways, splitting between seller and platform. Mangopay models this with users, e-money wallets, pay-ins, and transfers; this connector lets FlowRunner agents operate that model end to end. Agents onboard natural users, create and inspect wallets, confirm pay-ins settled, and execute the split, with the sideways move, the one that allocates real money between parties, held to human review where the stakes demand it. - Onboard sellers and buyers as natural users with the fields Mangopay's KYC requires - Create and inspect e-money wallets per user and currency - Confirm card and bank-transfer pay-ins settled before releasing goods or services - Move funds between wallets with configurable platform fees on each transfer - Pull user and wallet balances into daily reconciliation reporting The transfer is where FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) orchestration earns its place: allocation between parties is the decision a marketplace lives on. Sequencing is the quiet value in all of this. Pay-in confirmed before goods release, balance verified before transfer, transfer before payout: Mangopay's model assumes an operator who respects the order of operations, and an orchestrated flow is that operator, every time, including the fourth time on a busy Friday afternoon.

Without FlowRunner

Goods released on faith The seller ships when the order appears, not when the money actually settles

Splits computed in a spreadsheet Someone calculates seller shares and platform fees by hand, then keys transfers one at a time

Wallet balances checked by login Reconciling who holds what means clicking through the dashboard user by user

With FlowRunner

Settlement confirmed before release Agents poll the pay-in and verify credited funds, so goods move only after money does

Splits executed by rule Transfer amounts and fees compute from the flow's logic and execute the same way every time

Balances reported on schedule Wallet positions across all users flow to the reconciliation sheet daily

Use Case Scenarios

Seller onboarding from form to wallet

A new seller application arrives from [Typeform](/integrations/typeform). The agent maps the fields into Create Natural User, name, email, birthday as a Unix timestamp, nationality and residence as ISO country codes, the details Mangopay requires for a usable KYC level, then calls Create Wallet in the marketplace's currency. The seller ID and wallet ID flow back into the onboarding record, and a seller who applied in the morning can be paid by the afternoon.

The settlement gate in front of fulfillment

An order completes and the flow holds fulfillment while Get PayIn polls the payment. CREATED means keep waiting; FAILED routes to the buyer with a clear retry path; SUCCEEDED releases the goods and posts the confirmation to [Slack](/integrations/slack). The one rule a marketplace cannot afford to break, never ship against unsettled money, stops depending on a person remembering to check.

The daily wallet reconciliation

Each morning, the agent walks List Users, calls List User Wallets for each, and writes every wallet's ID, currency, and balance, in minor units, converted for the report, to [Google Sheets](/integrations/google-sheets). The platform's fees wallet gets its own line and a comparison against expected fee revenue. Drift between what the ledger says and what the wallets hold surfaces in a morning digest, while the discrepancy is hours old instead of a quarter old.

Human-in-Loop Highlight

Create Transfer moves e-money between wallets, and its parameters are exactly the ones you do not want wrong: an amount in minor units, where 1000 means 10.00 EUR and a factor-of-a-hundred mistake is one missing zero away, and a fee that is deducted from the debited funds and credited straight to the platform's fees wallet. A wrong transfer is not a display bug; it is money sitting in the wrong party's wallet, and unwinding it means another transfer, an awkward conversation, or both. So FlowRunner agents execute routine, rule-derived splits automatically and pause everything else: amounts above threshold, first payouts to a new seller, and any transfer whose computed fee deviates from the standard rate. The finance owner sees debited wallet, credited wallet, amount, and fee in plain currency terms, and approves. The split executes in seconds either way; the difference is that the irreversible ones were seen by someone accountable first.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

8 actions

Users

List Users Retrieves all users registered under the account, natural persons and legal entities, with ID, person type, KYC level, and creation date, paginated. The base read for reconciliation sweeps.
Get User Retrieves one user in full by ID, including person type, KYC level, and profile attributes. The verification step before wallets and transfers.
Create Natural User Creates an individual person with the fields Mangopay requires for a usable KYC level: name, email, birthday as a Unix timestamp, nationality and residence as ISO 3166-1 alpha-2 codes. The onboarding write.

Wallets

List User Wallets Retrieves all e-money wallets a user owns, each with ID, description, currency, and balance in minor units. The per-user position read.
Create Wallet Creates a wallet for a user in a single, permanent currency. The setup step that gives onboarded users somewhere to be paid.
Get Wallet Retrieves one wallet with owners, currency, and current balance in minor units. The funds check before any transfer or release.

Money Movement

Create Transfer Moves funds between two same-currency wallets, with a fee deducted from the debited funds and credited to the platform's fees wallet. Amounts in minor units. The operation this page's human gate exists for.
Get PayIn Retrieves a pay-in by ID with status, CREATED, SUCCEEDED, or FAILED, debited and credited funds, fees, and result codes. The settlement check that gates fulfillment.

Frequently Asked Questions

What can FlowRunner do with Mangopay?

FlowRunner agents can run List Users, Get User, and Create Natural User in Mangopay, plus 5 more actions.

Does connecting Mangopay to FlowRunner require OAuth?

Yes. Mangopay connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can Mangopay trigger a FlowRunner workflow automatically?

Mangopay doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Mangopay

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us