Easypay

Easypay is a Portuguese payment gateway covering Multibanco, MB WAY, cards, direct debit, and wallets. Agents create single and frequent payments, run subscriptions and Pay by Link checkouts, capture, void, and refund, and reconcile settlements and out payments.

59 actions API key available

Easypay website Platform Documentation Capability data verified 2026-08-25

An order is placed and needs collecting on Portuguese domestic rails

Agent reads the total, the customer, and the method the buyer chose

Create Single Payment issues the charge with an expiry set on the reference

Get Single Payment confirms the state before anything downstream moves

The settled transaction is matched into the ledger and the order released

The settlement batch is reconciled against the bank transfer and reported

A person decides how to hold a customer's subscription, because the pause deletes its schedule

What This Integration Enables

Easypay covers the Portuguese domestic rails, and the useful thing about it is that it refuses to pretend those rails are interchangeable. Multibanco, MB WAY, cards, direct debit, and the wallets differ in how they are created, how long they stay payable, and what canceling one actually does. A card authorization voids at once. A Multibanco reference closes on a published daily schedule. A direct debit cancellation only lands if the request arrives before the afternoon cutoff in Lisbon. Building a workflow that ignores those differences produces a system that reports success and leaves references live.

FlowRunner agents work at that level of detail. They create single and recurring payments, hold funds with an authorization and capture later, run subscriptions and their individual billing cycles, deliver hosted checkouts and Pay by Link, refund and track chargebacks within the per-method deadlines the API enforces, and reconcile the ledger against settlement batches. Money-out is signed with a separate key, which is a good sign of how the vendor thinks about it. And one operation on the subscription surface destroys a schedule while looking like a pause, which is exactly where human-in-the-loop belongs.

Without FlowRunner

References that never close A Multibanco reference is created without an expiry and stays payable months after the order was written off

Cancellation assumed to be instant A payment is deleted and treated as canceled, whatever the method's actual timing

Bank line matched to nothing The transfer arrives as one figure and nobody can say which transactions are inside it

With FlowRunner

References expire deliberately Every reference carries an expiry, and one created without it can have one added

Cancellation understood per method The workflow knows a card void is immediate and a direct debit cancellation has a daily cutoff

Settlements opened up Each transfer is read back to the transactions inside it, so the bank line reconciles to the ledger

Use Case Scenarios

A reference that closes when the order does

An order in WooCommerce chooses Multibanco. The agent calls Create Single Payment with an expiry set on the reference, because a Multibanco reference created without one can be paid months later, long after the order has been abandoned and written off. If a reference is already live without an expiry, Update Single Payment can add one. When the payment lands the agent releases the order and writes the row to Xero. Where the customer never pays, the deletion path is chosen by method: a card authorization voids at once, a Multibanco reference closes on the vendor's schedule, and a direct debit needs the request in before the daily cutoff.
The bank line, opened up

Finance sees one transfer. The agent turns it back into detail. List Settlements gives the batches, and filtering Get Ledger Report by the transfer batch shows exactly which captures, fees, chargebacks, and reward movements are inside it, each with gross, fee, tax, and net. The reconciliation lands in Google Sheets with the bank line matched to its components, and any unmatched movement posts to the finance channel in Slack. The ledger is the accounting source here, and the older transaction report is treated as a compatibility path for existing flows rather than something new work should be built on.
Card on file for variable amounts

A services business bills different amounts every month. Rather than a fixed subscription, the agent creates a frequent payment mandate once, checks the mandate's method status before charging because a card mandate waits until the customer has entered their details at the URL Easypay returned, and then calls Request Frequent Authorisation for each period's actual figure. The descriptive text on each authorization is set to the trading name, because that is what appears on the customer's bank statement and in their MB WAY app, and an internal job code there generates a support call rather than a payment.

Human-in-Loop Highlight

The most dangerous operation on this connector does not look dangerous. A customer asks to pause their subscription for two months, and the obvious move is Update Subscription with the status set to inactive. That is not a pause. Easypay deletes the pending cycles, and reactivating afterward requires the frequency and the start time all over again, because the platform schedules a fresh cycle rather than restoring the one it removed. Whatever the original schedule encoded, a mid-month billing date agreed with the customer, a run of cycles already repriced with a one-month discount through Update Subscription Cycle, is gone, and no operation on this connector brings it back. The agent therefore never sets that status on its own. It reads the subscription and its remaining cycles first, then posts: "Aurora Studios asked to pause billing until January. Setting the subscription inactive deletes 4 pending cycles, including the December cycle repriced to 40 euros for the promotion. Reactivation will need a new frequency and start time and will not restore those. Move the renewal date instead, delete the subscription and rebuild it in January, or proceed with inactive?" The account manager answers in one line. The reading, the cycle list, and whatever is chosen afterward are the agent's work. The write that silently discards a customer's agreed schedule is not.

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

59 actions

Single Payments

Create Single Payment Creates a one-off charge across Multibanco, MB WAY, cards, direct debit, or the wallets. The type decides whether it captures immediately or only holds the funds for a later capture, which is the most consequential choice on this connector.
List Single Payments Lists single payments. Date filters travel as one interval capped at thirty days, assembled here from an ordinary pair of dates.
Get Single Payment Reads one payment and its current state.
Update Single Payment Updates a payment. It cannot change the value or the method, which means a new payment, but it can add an expiry to a reference created without one.
Delete Single Payment Cancels a payment. What that means depends on the method: card and MB WAY authorizations void at once, Multibanco references close on a published daily schedule, and direct debit only cancels if the request lands before the afternoon cutoff in Lisbon.

Frequent Payments

Create Frequent Payment Creates a card-on-file mandate that can be charged repeatedly for varying amounts.
List Frequent Payments Lists mandates on the account.
Get Frequent Payment Reads one mandate, including the method status that says whether the customer has completed their details yet.
Update Frequent Payment Updates a mandate's configuration.
Delete Frequent Payment Cancels a mandate so it can no longer be charged.
Request Frequent Authorisation Charges a mandate for a specific amount. The descriptive text is required and appears on the customer's bank statement or in their MB WAY app, so it should carry the trading name rather than an internal code.

Holds, Captures and Voids

Get Authorisation Reads the state of a held authorization.
Capture Payment Takes money that was held by an authorization. An authorization left uncaptured lapses and nobody pays, which is the quietest way to lose a sale here.
List Captures Lists captures, paging by cursor rather than by page number.
Get Capture Reads one capture and its outcome.
Cancel Capture Cancels a capture. The vendor documents this operation as still rolling out, so treat a refusal as expected rather than as a fault.
Update Capture Split Adjusts how a captured amount is split between recipients.
Void Authorisation Releases a held authorization deliberately, freeing the customer's funds. It takes the authorization token rather than a void identifier, and it processes asynchronously.
Get Void Reads the outcome of a void, which is where an asynchronous release is confirmed rather than assumed.

Refunds and Chargebacks

Refund Payment Refunds a capture. It takes the capture's identifier rather than the payment's, and the API refuses a refund past the method's own deadline, which differs sharply between cards, Multibanco, and direct debit.
List Refunds Lists refunds with cursor paging.
Get Refund Reads one refund and its state.
List Chargebacks Lists chargebacks raised against the account.
Get Chargeback Reads one chargeback with its detail.

Subscriptions and Cycles

Create Subscription Creates a recurring schedule. Exactly one end condition is required, an expiry, a maximum number of captures, or unlimited, and the request is refused without one.
List Subscriptions Lists subscriptions, paging by page number.
Get Subscription Reads one subscription with its frequency, retry policy, and state.
Update Subscription Updates a subscription. Setting the status to inactive deletes the pending cycles rather than pausing them, and reactivation schedules fresh ones instead of restoring what was removed. This page's human gate sits here.
Delete Subscription Ends a subscription outright.
List Subscription Cycles Lists a subscription's individual billing cycles with cursor paging.
Get Subscription Cycle Reads one cycle and its state.
Create Subscription Cycle Bills a one-off against the stored method without touching the schedule, which is how a setup fee, an add-on, or an upgrade is charged.
Update Subscription Cycle Reprices a single cycle, which is how a one-month discount is applied. Only a renewable cycle still pending can be repriced.

Checkout and Pay by Link

Create Checkout Creates a hosted payment page for a transaction. The type is an array but only its first entry counts, so a second value changes nothing.
Get Checkout Reads a checkout session and its state.
Delete Checkout Cancels a checkout session.
Create Payment Link Creates a hosted page and has Easypay deliver it by SMS or email through the communication channels on the request. A workflow with a phone number and an amount needs nothing else.
List Payment Links Lists payment links with cursor paging.
Get Payment Link Reads one link and its state.
Update Payment Link Changes a link's expiry. Everything else means creating a new link.
Delete Payment Link Deletes a link, irreversibly.

Out Payments

Create Out Payment Sends money out of the account. It is signed with a separate private key over the exact request bytes and carries a timestamp that must be within a minute of real time, which is a fair indication of how the vendor treats money leaving.
List Out Payments Lists outbound payments.
Get Out Payment Reads one outbound payment and its state.
Delete Out Payment Cancels an outbound payment that has not executed. This one is signed over the identifier rather than the body.

Reporting and Settlements

Get Ledger Report Returns one entry per movement with gross, fee, tax, and net, separating captures from fees from chargebacks from reward movements. The accounting source of truth on this connector.
Get Transaction Report The older reporting route, kept so existing workflows keep running. The vendor has published its end of life and points new work at the ledger.
List Settlements Lists settlement batches, each grouping the transactions paid out in a single bank transfer. The layer that matches your bank statement.
Get Settlement Reads one settlement batch, which is how a single bank line is opened back up into the transactions inside it.

Customers and Rewards

Get Customer Reads a customer record back by the identifier a payment returned. There is no way to create, list, or search customers here, because a customer record appears as a side effect of a payment.
List Customer Rewards Lists a customer's reward balance movements.

Terminals

Create Terminal Registers a physical payment terminal on the account.
List Terminals Lists registered terminals.
Get Terminal Reads one terminal's configuration.
Update Terminal Updates a terminal's configuration.
Delete Terminal Removes a terminal from the account.

Account

Get Account Config Reads the account configuration, including the notification URLs.
Update Account Config Updates the account configuration. The notification URLs here are account-wide singletons with one per kind, so changing one redirects every notification of that kind away from whatever was already receiving it.
Ping Confirms the connection and credentials are working, which is the cheap check before a batch run rather than after it fails.

Frequently Asked Questions

What can FlowRunner do with Easypay?

FlowRunner agents can run Create Single Payment, List Single Payments, and Get Single Payment in Easypay, plus 56 more actions.

Does connecting Easypay to FlowRunner require OAuth?

No. Easypay connects to FlowRunner with an API key, no OAuth flow required.

Can Easypay trigger a FlowRunner workflow automatically?

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

Start building with Easypay

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us