Product

Cross-Border Payments API

One integration to move money between currencies in about a minute, settled over the Bitcoin Lightning Network — with no pre-funded float accounts. Fiat in, fiat out by default; Bitcoin and USDT if you prefer.

0.8%
Fees starting at
~1 min
Typical settlement
$0
Float required
Book a Demo Request API documentation
In practice

A payment in three calls

Quote the rate, create the payment, and let the webhook tell you when it settled.

POST /quote

Check the live rate and what the recipient receives before committing to anything. Nothing moves yet. 

{
  "amount": 10,
  "destinationCurrency": "ZAR",
  "sourceCurrency": "KES"
}
POST /payments

Create the payment against a saved recipient. The rate is locked at creation, and a reference is required for South African payouts. 

{
  "merchantId": "9f430126-99da-42e8-afb1-4cab619cda5a",
  "amount": 100,
  "reference": "INV12345",
  "webhookUrl": "https://your-server.com/webhooks/payments"
}
POST your webhookUrl

We post an event to your endpoint each time the payment changes status, so you never have to poll for settlement. 

{
  "paymentId": "eafdea43-63a7-4f61-b8ae-823c1b3aa236",
  "status": "success",
  "log": "payment has been completed successfully"
}

What is a cross-border payments API?

In short

  • One API for every corridor, rather than one integration per country.
  • Fiat both ends unless you choose otherwise — Bitcoin and USDT are supported too.
  • No pre-funded accounts, so working capital stays in your business.
  • Settlement in about a minute, most corridors.

A cross-border payments API lets software move money between countries and currencies without anyone logging into a banking portal. Your system makes a request; the provider converts it, pays out locally and reports back.

Businesses reach for one because of what sits behind it. Traditional transfers hop through correspondent banks, each adding a fee and a delay, and most providers make you pre-fund an account in every destination country. That capital sits idle and grows with every corridor.

Djingr's API removes both. Payments settle over the Bitcoin Lightning Network instead of correspondent banks, so settlement takes about a minute rather than days — and because value moves at the moment of the transaction, there is no float to maintain.

A software engineer at a two-monitor workstation at dusk, one screen showing code and the other a payment route between two points, with a city skyline beyond the window.
How it works

From API call to local settlement

Three steps, and the middle one is invisible unless you choose otherwise.

1. One API call

Your system sends a payment instruction through a single unified API — the same integration regardless of which corridor the money is going to.

2. Fiat-to-fiat by default

The value moves across the Bitcoin Lightning Network and out into the destination currency. Bitcoin is the rail, not something you have to hold — though you can send or receive in Bitcoin or USDT if you prefer.

3. Local settlement

Funds arrive in a local bank account or mobile money wallet in the destination market, typically within a minute.

Coverage

Currencies, fees and settlement times

Fees vary by route. These are the published ranges by origin currency.

Origin currency Fees (destination dependent) Settlement
BTC (Lightning)0.5%–1%< 1 min
ZAR0.75%–1.25%1 min
EUR1.1%–1.6%< 5 min
GBP1.1%–1.6%< 5 min
USDT (ERC20)1.1%–1.6%1 min
KES1.3%–1.5%1 min
NGN1.3%–1.8%1 min

What does integrating the API involve?

The integration model is deliberately narrow. One unified API covers every corridor, so adding a destination market is a configuration change, not a new integration project — unlike stitching together a local provider per country, each with its own interface and reconciliation quirks.

By default your systems send and receive fiat; the Lightning leg is handled entirely on our side, so nothing in your stack has to understand Bitcoin or hold a wallet. That is a default, not a limit: fund or pay out in Bitcoin or USDT and the API handles it too. Teams wanting no engineering time at all can deploy the whitelabel payments platform instead.

Documentation and integration support come directly from our team, scoped to the corridors and volumes you need.

Two engineers at a shared desk reviewing an integration together, one pointing at a monitor, with a city skyline beyond the window at dusk.

Get the integration documentation

Tell us which corridors you need and we will send the integration documentation along with indicative pricing for your volumes.

Request API documentation
Comparison

How is this different from traditional payment rails?

Criterion Correspondent banking Djingr API
Settlement time1–5 business daysAbout a minute
Capital requiredPre-funded account per marketNone
IntegrationsOne per provider or countryOne, for all corridors
Weekend settlementNext business daySame as any other time
FeesStacked across intermediariesFrom 0.8%, no platform fee
FAQ

API questions

Which currencies and corridors does the API support?
ZAR, NGN, KES, GBP, EUR, USDT and Bitcoin over Lightning, with settlement live across South Africa, Nigeria, Kenya, the United Kingdom and Europe.
Do we or our customers have to touch Bitcoin?
No. The default flow is fiat in, fiat out — Bitcoin Lightning is the rail underneath and nothing in your stack has to handle it. If you or your end users would rather fund or receive a payment in Bitcoin or USDT, that is supported as well.
Do we need to pre-fund accounts to send payments?
No. Value moves at the moment of the transaction over the Lightning Network, so there is no float to hold in any destination country and no working capital tied up per corridor.
Is there a monthly minimum spend per account?
No. There are no monthly minimums and no platform fees on any corridor — you pay only the per-transaction fee for the route you use, from 0.8%.
What does integrating the API involve?
A single unified API covers every corridor, so it is one integration rather than one per country. Our team provides documentation and support throughout the process.
Can we use Djingr without building our own interface?
Yes. Alongside the API we offer a whitelabel web app that can be deployed without writing code, for teams that want to launch quickly.
Is the API suitable for regulated financial institutions?
Djingr is built for licensed institutions and adheres to local financial regulations in the markets where it operates.

Move money without the float

We will show you how the Djingr API fits your corridors — no float, no delays.

Book a Demo