Send business payments out to your recipients over schemes that settle instantly where those schemes are supported, and over standard routes everywhere else, from one interface.
A payout is money a business sends out: to a seller, a contractor, a supplier or a partner. It is the outgoing direction of payments, as opposed to the incoming side, where a client pays you on details you published. Same schemes, opposite direction.
An instant payout is one carried over a scheme built to settle outside the standard banking cycle rather than in the next processing window. That is a property of the scheme, not a service tier, and not something a platform can promise alone: the route involves the recipient's bank as much as us.
Instant payouts depend on four conditions holding at the same time. Miss one and the payment settles on a standard cycle instead.
Some payment schemes settle outside business hours, others do not. SEPA Instant is one of the first kind; a standard transfer follows the banking cycle.
Participation is per institution. If the recipient's bank is not on that scheme, payments cannot travel it, whatever the sending side supports.
Each scheme carries a per-payment ceiling. Above it, payments take a standard route, which is a scheme rule rather than an account setting.
A payout waits for approval inside your business, and for the screening that applies to payments. Neither step is skipped.
What people call instant payouts is a property of the route payments take, not of the tariff you are on.
The recipient is waiting, so they write to your support team about a payment nobody can find.
Payments pile up until somebody runs the batch at the end of the day.
Recipient data is typed by hand, and one wrong character turns into a returned payment.
Nobody can say where a payment is at any time, because there is no status to look at.
Payouts reconcile in one place and incoming payments in another.
Instant payouts and standard ones are prepared the same way on the platform; only the scheme underneath them differs.
Pick a saved recipient or add a new one, enter the amount, and see the fee before you confirm. Recipients you pay regularly are stored, so repeat payments are not a retyping exercise.
SEPA Instant, SEPA, SWIFT and internal transfers between
Fenryx accounts. Which one a payment takes follows the destination, the currency and the four
conditions above.
Payments are funded from a currency balance or an IBAN account your business holds, so funds are on the platform before a payout is created.
More than one user works the account. A payment can need release by a second person, and anything waiting sits at Waiting for approval until an authorised user acts.
Payouts carry a status through the platform, with the transaction detail behind them and an export that lines payments out up against payments in.
Funds sit on the balance the payments will come from.
Recipient data is entered once and saved for the next run.
Amount, currency and purpose, with the fee shown each time before you confirm.
Your own release step, then the compliance screening that applies to every payment.
The status updates as each payment moves, and the record exports.
Sellers are paid on a cycle they can plan around, and payouts carry a status they can be told about. Sellers stop asking where the money is, which is most of that support load gone.
A platform with contributors in several countries runs one batch instead of a queue of separate payments. Saved recipients mean the second month costs a fraction of the first.
Suppliers invoice in their own currency and get paid from the balance that already holds it. Where a scheme with instant settlement does not reach them, payments go over a standard cross-border route.
Regular batches, approvals recorded against each payment, and one export that matches payouts to the incoming side at close.
| Item | For your account |
|---|---|
| Fee, instant scheme | Quoted per business, shown before you confirm |
| Fee, standard scheme | Quoted per business, shown before you confirm |
| Currency conversion | Rate and cost shown up front |
| Per-payment limit | Set at onboarding, within the scheme ceiling |
| Daily limit | Set at onboarding |
| Currencies | Agreed per account, see multi-currency accounts |
| Cut-off times | Apply to standard schemes, and vary by scheme and currency |
These are fixed for your business at onboarding rather than published as one price list, because schemes, currencies and limits are set around what a business pays out and where. Each time you send, the fee appears before you confirm.
Registered legal entities only. We do not open personal accounts or handle payments between individuals, so instant payouts here run from a business to its counterparties.
Availability depends on the business, its jurisdiction, where it pays and the outcome of KYB review. Screening applies to payments throughout, not only at onboarding.
A summary. See our AML Policy.
Schemes and currencies. Which ones a platform actually enables for your destinations.
The fallback. What happens when the instant scheme is not available for a recipient.
Limits. Per payment and per day, and how they relate to the scheme ceiling.
Roles and approvals. Who can create a payment and who can release it.
Export format. Whether the platform gives data back in a shape your books accept.
Instant payouts settle on the timetable of the scheme they travel, so it depends on that scheme, on whether the recipient's bank is reachable, and on the checks that apply. We publish no timings: the route decides them.
Payments take a standard scheme instead and settle on the usual banking cycle. Which routes reach a recipient is part of what gets configured for your account.
Yes, over SWIFT and the other schemes enabled for your account. Schemes that settle instantly are euro-denominated, so payments beyond that area follow a standard route.
Once payments have left, recall depends on the scheme and on the receiving side agreeing to return them. That is why approvals sit before sending, and why recipient data is checked twice.
Yes. Payouts are funded from the balance behind them, so money is on the account first. We do not advance funds or lend against a pending run.
Yes. Users get the rights your business needs, so one person prepares payments and another releases them, each time.
Tell us who your business pays and where they are, and we will get started.
Fenryx is operated by Globally United Tech Corporation, a money services business registered with FINTRAC in Canada. Fenryx is not a bank and does not provide banking services. Settlement speed depends on the payment scheme used and on the recipient's bank, and availability depends on jurisdiction, business activity and KYB review.