Transfer model
Marketplaces
Accept buyer funds, preserve transaction context and connect collection to split and payout workflows.
AcceptanceSplitsPayouts
Payment gateway
Turn payment acceptance into a controlled end-to-end workflow.
Connect checkout, provider routing, transaction status, fees, reconciliation and settlement so merchants and operations teams see one coherent payment product.
One product layer across payment providers
Routing and fallback rules
Unified status and reconciliation
Merchant and operational visibility
A complete transfer workflow
Transfer createdBeneficiary · details verified£12,000
Transfer route
GBP → EUR
Recipient
€13,980
Transfer ready to route
Transfer orchestration
A transfer is more than a payment instruction.
The complete product needs consistent transaction identifiers, clear state transitions, provider-level observability, ledger posting, reconciliation and merchant settlement. Framnex connects these jobs in one workflow.
Step 1
Set up
Create a beneficiary and capture the required account details.
Step 2
Validate
Apply the checks and validations required for the selected route.
Step 3
Route
Choose the currency, corridor and transfer path for the payment.
Step 4
Track
Follow the transfer status through to its destination outcome.
Transfer model
Digital platforms
Embed payment initiation and status into an existing software journey.
CheckoutAPIsReconciliation
Transfer model
Payment providers
Add orchestration, merchant visibility or new provider routes around an existing acquiring proposition.
RoutingFallbackSettlement
Capabilities
Build transfer operations around recipient, route and status — not manual handoffs.
Choose the components that solve the immediate customer need, with the option to connect more services as the product grows.
Payment acceptance
Create checkout and payment instructions with the metadata required for routing and downstream operations.
Orchestration and fallback
Apply provider selection, retry and fallback logic without exposing a fragmented experience to the merchant.
Refunds and disputes
Connect reversals, refunds, exceptions and dispute states to the original transaction and customer context.
Reconciliation and settlement
Match external provider records to the internal ledger, fees and merchant payout obligations.
Payment lifecycle
Keep one internal transaction truth while providers behave differently.
The orchestration layer translates provider events into stable product and operational states.
Create
Create a canonical payment
Assign one internal identifier and store customer, merchant and order context.
Route
Select the provider path
Apply eligibility, cost, geography, method and resilience rules.
Observe
Track every external event
Normalize authorisation, capture, failure, refund and dispute updates.
Settle
Reconcile funds and obligations
Match provider reports to ledger entries, fees and merchant payouts.
Transfer operations
Make cross-border money movement easy to understand and operate.
Bring beneficiary setup, route selection and a clear final status into one operational transfer view.
Launch path
Start with a clear first workflow.
A focused launch makes it easier to align commercial owners, operations and product teams before adding more complexity.
- 1Define the acceptance eventMap the customer action, payment method, merchant model and confirmation required for the first use case.
- 2Choose routing and state rulesDefine provider selection, retries, timeouts and the internal status model before integration.
- 3Connect ledger and reconciliationEnsure successful, failed, refunded and disputed payments create traceable financial events.
- 4Add providers from measured needExpand routes where approval, geography, cost or resilience data justifies the change.
Payment gateway FAQ
Questions about this solution.
The commercial and operational questions teams most often ask before outlining their first launch.
Can Framnex work with payment providers we already use?
Yes, where suitable APIs and operational data are available. The connector and orchestration layer can preserve existing relationships while creating a more consistent product model.
Do we need multiple providers at launch?
Not necessarily. The architecture should make additional providers possible, but the first release can use one route when that is operationally clearer.
Is reconciliation part of the gateway?
It should be part of the end-to-end design. Provider responses alone do not confirm that external reports, ledger entries, fees and settlement obligations match.
Can the same workflow support merchant payouts?
Yes. Collection and payout workflows can be connected so eligible funds, fees, reserves and settlement status flow into recipient payments.
Start with a discovery call
Ready to explore what's possible?
In a 15-minute discovery session, we'll discuss your business model, customer needs and commercial objectives to determine the right foundation for your financial offering.
No technical preparation required
Business-focused discussion
Tailored recommendations
No obligation