Use case

Cross-border payments for fintechs

Add international transfers to your product without pre-funded accounts or a banking partner in every market. Your customers stay in fiat by default, or can send and receive in Bitcoin or USDT if you enable it.

0.8%

Fees starting at

~1 min

Typical settlement

$0

Float required

Book a Demo

What makes cross-border payments hard to build?

Adding international transfers to a fintech product is rarely blocked by the front end. It is blocked by what sits behind it: a banking partner in each destination market, settlement and reconciliation logic, and capital pre-funded in every country you want to pay into.

That work scales with geography rather than volume. The second corridor costs roughly what the first one did, which is why many products launch with one or two and then stop.

Djingr replaces the per-market work with one integration. Payments settle over the Bitcoin Lightning Network, so opening a corridor is a configuration change rather than a new partnership — and there is no float to fund in any of them.

A single connection point branching into several corridor lines converging on distant markers, representing one integration opening many payment corridors.

Why fintechs use it

Three constraints removed

These are usually the three things that decide whether a corridor gets built at all.

One integration, every corridor

The same integration covers each supported market, so adding a destination does not mean adding a provider.

No pre-funding

No capital sits in destination accounts waiting to cover payouts, so corridors stop competing for working capital.

Fiat by default

Your users send and receive fiat by default, with Bitcoin as the rail underneath and nothing for them to hold or understand — though you can offer Bitcoin or USDT funding if you want to.

What are the two ways to build cross-border payments?

If the payment experience belongs inside your own product, integrate the cross-border payments API and design the flow yourself. Your systems send fiat and receive fiat; the Lightning leg is handled entirely on our side.

If being live sooner matters more, the whitelabel payments platform deploys without engineering work and runs on the same corridors and pricing. Launching on whitelabel to prove demand and integrating the API later is a reasonable sequence.

Settlement is live between South Africa, Nigeria, Kenya, the United Kingdom and Europe, plus Tether and Lightning. Fees start at 0.8% and vary by route, with no platform fees and no monthly minimums.

Two paths diverging from one starting point on a dark surface, one leading toward a small pre-built interface panel, the other toward an open, unbuilt frame.

FAQ

Common questions

Do our customers need to know anything about Bitcoin?

Not by default. Your users send and receive fiat currency, with Bitcoin as the settlement rail underneath and nothing shown or held on their side — though you can offer them Bitcoin or USDT funding if you choose to.

Do we need a banking partner in each market?

No. One integration covers every supported corridor, which is the main difference from assembling a local provider per country.

How much capital do we need to open a corridor?

None held in the destination. Value moves at the moment of the transaction, so there is no pre-funded float per market.

Should we start with the API or the whitelabel app?

The API if the payment experience must live inside your own product; the whitelabel app if you want to launch without engineering time. Both run on the same infrastructure, so you can move between them.

Which corridors are available today?

Settlement is live between South Africa, Nigeria, Kenya, the United Kingdom and Europe, plus Tether and Lightning.