Platforms and marketplaces
Teams designing seller withdrawals, supplier disbursements or other multi-party payout journeys across one or more markets.
Interlink · Planning · partner enquiries open
Programmable routes for modern payouts.
Payout connectivity in development for platforms and payment partners. Bring requests, routing, checks and transaction updates together as you expand across markets.
Discuss a route
Meet Interlink
The connections behind better payouts.
Payout infrastructure in development for platforms, marketplaces and embedded-finance teams connecting payments across markets and partners.
Interlink is in development, not a live self-service payout API. Availability will depend on the markets, partners and operating requirements.
- What it is
- Payment connectivity, partner coordination and transaction visibility
- Built for
- Platforms, marketplaces, embedded-finance teams and partners
- Current stage
- Corridor, integration and partner planning by enquiry
How it works
From payout request to operations.
See how the parts fit together, then explore each stage of the approach.
- The platformMarketplace, supplier or embedded payout request
- InterlinkRoute policy, partner coordination and transaction events
- Payment partnersMarket-specific connectivity and operating responsibilities
- Your operationsStatus, reconciliation and exception handling
Proposed model. Partners, responsibilities and market availability are agreed for each use case.
Explore the approach
Model the payout promise.
Start with who is paying, who receives, which markets are involved and what experience the platform intends to offer. The commercial flow comes before a technical connection choice.
- Participants and markets
- Payout experience
- Volume and service assumptions
Shape the route and responsibilities.
Map the route, partner roles, controls and decisions that need to hold together. A viable route is more than connectivity—it has ownership, eligibility and exception rules.
- Corridor and partner map
- Route policy
- Clear responsibility model
Design the integration and event model.
Plan how the platform creates instructions, receives status and keeps the user experience aligned with what is happening across the route. The interface follows the operating model.
- API-oriented connectivity
- Event and status model
- Experience-to-operations alignment
Prepare for the imperfect path.
Reliable payouts depend on reconciliation, evidence, support and exception handling. Interlink discussions include the work needed to move from a promising route to an operable service.
- Exceptions and support
- Evidence and reconciliation
- Launch-readiness planning
1 / 4
Select a step to explore how the proposed platform is being shaped.
Who it’s for
For the teams moving the market forward.
Interlink is for teams on the business side of money movement—the people defining payout products, integrating systems, supporting corridors and operating the exceptions.
Embedded-finance builders
Product and engineering teams that want to start from the customer flow, then shape the connectivity, events and responsibilities behind it.
Network and corridor partners
Potential partners exploring where connectivity, operational coverage or commercial participation could strengthen a defined payout route.
Commercial node participants
Firms exploring liquidity support, network participation and wider payout coverage. Participation models, responsibilities and commercial terms would be assessed as the network develops; availability or returns are not guaranteed.
Why Interlink
Designed around what matters to you.
Interlink moves the conversation above isolated rail connections. It starts with the payout product and joins technology, partners and operations around that route.
Route before rail
Choose connectivity in the context of the experience, market and operating responsibilities.
One view of each payment
Plan statuses and evidence so product, support and finance teams are not working from different truths.
Adaptable participation
Define how platforms, developers and partners fit the route instead of forcing every use case into one role.
Operations included
Exceptions, reconciliation and support are designed with the route—not discovered after integration.
Ways to get involved
- Marketplace and supplier payouts
- Embedded-finance product planning
- Multi-market corridor exploration
- Developer, partner and network discussions
Not available today
- Individual consumer transfers
- An instant self-serve API key
- A corridor with no defined participants or use case
- Guaranteed availability before route assessment
Questions, answered
Get a clearer picture.
What exactly is Interlink?
Interlink is payout infrastructure in development. It is designed to connect payment instructions, partners, transaction updates and operating controls across markets.
Is Interlink a live payout API?
No. Interlink is in development. We are exploring specific markets, partners and operating requirements through enquiries.
Who should enquire?
Platforms, marketplaces, embedded-finance teams, developers and potential corridor or network partners with a defined payout problem should use the enquiry path.
What problems is it intended to address?
Examples include seller withdrawals, supplier disbursements, embedded payout journeys, multi-market status coordination and corridor or partner planning.
What should we bring to a first conversation?
Bring the markets, participants, desired payout experience, expected volumes and known compliance, support or operating constraints.
How does Interlink relate to SabPay?
Interlink is infrastructure for platforms and partners. SabPay is the planned consumer app, with a separate waitlist for launch updates.
Your next step
Let’s map your payout opportunity.
Share your markets, participants and payment use case. Start a focused conversation about connectivity, integration and partner opportunities.
Interlink is in development, not a live self-service payout API. Availability will depend on the markets, partners and operating requirements.Prefer a general conversation?