Processing is the operational chain behind a payment: initiation, routing, compliance checks, FX, settlement, statuses and reconciliation. This page walks the whole chain, stage by stage.
Almost nobody complains that an international payment exists. What companies complain about is not being able to see it. The money has left, the recipient says nothing has arrived, and between those two facts sits a chain of institutions none of which is talking to the person being asked the question.
The same payment to the same supplier takes a different length of time from one month to the next, because the chain it travels is not identical each time.
A payment leaves and then simply has no state. It is not confirmed, not returned, and not visible — so the finance team is answering questions with guesses.
Institutions in the middle of a SWIFT chain can deduct their own charges, so the amount credited is less than the amount sent and the difference surfaces only when the recipient says so.
Statements arrive without the reference each payment carried, so matching outgoing payments to invoices becomes a monthly assembly job across several sources.
Every corridor expects beneficiary data in its own shape, and a payment built for one destination is returned rather than corrected when it is sent to another.
Cross-border payment processing is the operational chain a payment travels once it leaves one country for another. It is not a single action. A payment is created, checked, screened, possibly converted, routed onto a payment rail, settled at the far end, and then recorded — and each of those is a distinct stage that can succeed, wait, or fail on its own terms.
Understanding the chain matters because responsibility is distributed along it. The company initiating a payment controls the first stage and almost none of the others. A provider controls how the payment is validated, screened, converted and routed. The rail carries it. Correspondent institutions may handle it in the middle. The receiving institution decides when the beneficiary account is credited. When somebody asks "why is this payment slow?", the honest answer is usually "which stage is it sitting in?" — which is exactly why a status on the payment is more useful than an estimated arrival time.
Seven stages, in the order a payment meets them. Each one carries its own reasons a payment can be held, so each is followed by a note on what tends to cause a delay there.
The payment instruction is created: a beneficiary, an amount, a currency, a reference, and the balance the payment will be funded from. At this point the payment exists only inside the sending platform and nothing has left the company.
Insufficient funds on the paying balance, or an internal approval that has not been given yet. A payment waiting for a second authoriser has not been delayed by anyone external — it simply has not been released.
Beneficiary details are checked against the shape the destination expects — an IBAN where the rail requires one, local details where it does not, and a beneficiary name matching the account being paid. Structural errors are far cheaper to catch here than after a payment has left.
Details in the wrong format for the corridor, a mismatch between the beneficiary name and the account, or a missing field the destination treats as mandatory. These are the most common causes of a payment being returned days later rather than stopped immediately.
The payment and the parties to it are screened as part of the regulatory obligations a provider operates under. This is a process step, not a formality bolted on afterwards, and it applies to payments throughout the life of an account rather than only at onboarding.
A check that requires additional information about the payment or the counterparty. Neither the outcome nor the duration of a review can be promised in advance, and we do not describe them as if they could be. What we can say is which stage the payment is sitting in.
Where the paying balance and the destination currency differ, a conversion happens before the payment leaves. Where they match — a euro balance paying a euro invoice — this stage does not occur at all, which is the practical argument for holding balances in the currencies you actually work in.
Currency market hours and non-working days on either side. A conversion instructed outside trading hours for a given pair waits for the market to open rather than executing against a stale price.
The payment is routed onto a rail that fits the destination: SEPA for euro payments inside the SEPA area, SEPA Instant where available, SWIFT for payments beyond it, and internal transfers where both sides hold accounts on the same platform. The rail determines who handles the payment next.
Cut-off times. A payment submitted after the cut-off for its rail joins the next cycle rather than the current one, which is why the same payment sent an hour apart can behave differently.
Funds reach the receiving institution, which credits the beneficiary account. On a SWIFT payment this may involve one or more correspondent institutions relaying the payment, each operating on its own schedule and, in some chains, deducting its own charges.
A correspondent handling the payment on its own timetable, a non-working day in the destination country, or the receiving institution applying its own checks before crediting the account. This stage is the one furthest outside any provider's control.
The payment reaches a final state and carries its detail, comments and reference into the record. That record is what the finance team reconciles against invoices, and whether the reference survives into the export decides whether reconciliation is a lookup or a reconstruction.
Nothing delays the payment at this stage — but a thin record delays the close. When references and payment detail are lost between the platform and the export, the work simply moves from the payment to the spreadsheet.
Fenryx is a digital finance platform and payment account provider. The whole chain above runs on one platform: accounts and IBAN details for receiving, multi-currency balances to pay from, conversion between those balances, SEPA and SWIFT for the payments themselves, approvals before release, a status on every payment, and an export that keeps the detail. Collection and payment sit in one place rather than two, which is what makes reconciliation a lookup instead of an assembly job.
We describe this as compliance-aware processing, and the phrase is deliberate. Screening is a stage inside the flow rather than a gate bolted on before it, and it applies to payments continuously rather than once at onboarding. What we will not do is promise an outcome or a duration for any individual check, because neither is ours to promise. What the platform gives you instead is the honest thing: visibility of which stage a payment is sitting in.
Some specifics depend on your account rather than on a published list. Which corridors are available, which collection and settlement currencies apply, how conversion is priced for your volumes, and whether higher-volume flows are served through file-based or programmatic routes — all of that is agreed during onboarding. If those details decide whether the platform fits, raise them in the first conversation and we will answer them plainly rather than in marketing terms. The wider product context sits on the cross-border payments platform and the cross-border payments solution.
The company applies online and sends documents remotely. Every account opens through KYB review, and screening continues for the life of the account.
Balances in the major currencies the business earns and pays in, so a payment can leave the balance already holding the invoiced currency. See multi-currency account.
Details of your own that clients and platforms abroad can pay into, so incoming funds land where the outgoing payments are managed. See IBAN account.
Payments travel the rail that fits the destination, with internal transfers between Fenryx accounts.
Convert between currency balances with the rate and the cost shown side by side, rather than folded into a single number.
Each payment moves through pending, waiting for approval, processing and finished, and release can require a second authorised user.
Payment detail, comments and references survive into the export, so the accounting side receives context rather than amounts.
A company invoicing customers in several countries, receiving on IBAN details of its own and holding each currency rather than converting every payment on arrival.
Processor and marketplace settlements arrive, supplier payments leave the same balances, and both directions appear in one record at the end of the period.
Collection from buyers and payouts to sellers running on the same platform, so the money coming in and the money going out are reconciled against each other rather than separately. See international payouts.
A product whose own users are legal entities, settling them from balances the company holds instead of routing every payment through a general-purpose institution.
One place to see the status of every outgoing payment regardless of which corridor it travels, and one export covering all of them at period close.
Tell us which corridors and currencies your payments touch, and we will map them against what the platform actually covers — before any paperwork starts.
Discuss cross-border processingRelated reading: cross-border payments solution and international business accounts.
The flow above is the path a payment takes. This is the path you take — six steps from first conversation to a reconciled period.
Tell us which countries and currencies your payments touch.
The company, its owners and its activity profile are verified.
Balances, IBAN details, users and access are configured for your flows.
Fund a balance, add a beneficiary, and send the first payment through the chain.
Follow each payment by status rather than by estimate.
Export the period with references and payment detail intact.
| Account fee | Quoted per account at onboarding |
| Transaction fees | Quoted per rail, shown before you confirm a payment |
| Currency conversion | Rate and cost shown side by side, not folded into the rate |
| Correspondent charges | Where a chain applies them, they sit outside our pricing and we say so rather than absorbing the question |
| Limits | Set at onboarding, reviewed against real activity |
| Settlement timing | Depends on the corridor, the rail and the receiving institution |
Final terms depend on the business profile and the corridor, so pricing is agreed at onboarding rather than published as one price list. Where a number cannot honestly be given in advance, we would rather say that than publish one that does not hold.
Registered legal entities only. We do not open personal accounts, and payments run from a company to its counterparties rather than between individuals.
Eligibility depends on business type and jurisdiction, on the corridors a company pays into and receives from, and on the outcome of KYB review. Sanctions screening and anti-money-laundering checks apply to accounts and to payments on an ongoing basis, in line with the obligations we operate under. Fenryx is operated by Globally United Tech Corporation, a money services business registered with FINTRAC in Canada — that is the regulatory statement we make, and we make no claims beyond it.
A summary. See our AML Policy.
A neutral comparison of operating models, not a claim that either is universally better. The right choice is the one whose shape matches how a company actually moves money.
Worth asking either kind of provider: which rails do you actually run, which currencies can I hold, do I get payment details of my own, is FX cost shown separately, and can two people be required to release a payment?
The operational chain a payment travels once it leaves one country for another: initiation, validation of recipient data, compliance checks, currency conversion where needed, routing onto a payment rail, settlement at the receiving institution, and the status and reconciliation that follow.
In seven stages, each with its own reasons a payment can be held. They are set out in full, with the delay causes for each, in the process flow section above.
Most delays trace to one of four things: beneficiary details that do not match what the destination expects, a compliance check that needs more information, a correspondent institution handling the payment on its own schedule, or a cut-off time and non-working day on one side. Each stage above names its own.
Where the paying balance and the destination currency differ, a conversion happens before the payment leaves, and the rate and the cost are shown side by side rather than folded into one number. The pricing approach for your volumes is agreed at onboarding — we do not publish rate promises. Holding balances in the currencies you work in, as described under multi-currency accounts, avoids the stage entirely.
Each payment carries its own status on the platform, moving through pending, waiting for approval, processing and finished. That answers "where is it?" at any moment, rather than offering an estimated arrival that may not survive a correspondent chain.
SEPA for euro payments inside the SEPA area, SEPA Instant where available, SWIFT beyond it, and internal transfers between Fenryx accounts. Which rails and corridors apply to a given account is confirmed at onboarding rather than promised across the board.
Tell us which corridors and currencies your payments travel, and how you need them reconciled.
Fenryx is operated by Globally United Tech Corporation, a money services business registered with FINTRAC in Canada, Vancouver, BC. Corridor availability, currencies, rails and limits depend on business type, jurisdiction and KYB review. Settlement timing depends on the corridor, the rail and the receiving institution. Nothing on this page is legal, tax or regulatory advice.