Skip to main content
POST
Create crypto bridge deposit (Cross-border remittances)

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
customer_key
string
required

Customer key (Provider customer ID in Kotani system)

Example:

"PROVIDER_CUSTOMER_123"

provider_reference_id
string
required

Provider's unique transaction reference ID

Example:

"PROVIDER-TXN-20241122-001"

amount
number
required

Source fiat amount

Example:

1000

source_currency
string
required

Source fiat currency code

Example:

"KES"

wallet_id
string
required

Kotani wallet ID to use for transaction

Example:

"KOTANI_WALLET_ID"

transaction_type
enum<string>
required

Type of bridge transaction

Available options:
cross_border,
bridge,
chain_settlement
Example:

"cross_border"

chain
enum<string>
required

Blockchain/network to use

Available options:
CELO,
ETHEREUM,
ARBITRUM,
AVALANCHE,
BINANCE,
POLYGON,
OPTIMISM,
FUSE,
TRON,
PROVENANCE,
SOLANA,
HEDERA,
STELLAR,
BASE,
LISK,
VICTION,
SCROLL,
LIGHTNING
Example:

"LIGHTNING"

token
enum<string>
required

Token/asset to use

Available options:
CUSD,
USDC,
USDT,
BUSD,
HASH,
HBAR,
USDGLO,
CKES,
CGHS,
MSAT
Example:

"MSAT"

crypto_payment
object
required

Crypto payment details (pre-generated invoice or address)

settlement
object
required

Settlement details for recipient

callback_url
string
required

Callback URL for status updates

Example:

"https://api.provider.com/webhooks/kotani/status"

rate_id
string

Rate ID from /rate/crypto-bridge endpoint. Optional but recommended. Validates fiat->crypto conversion rate. Rate expires in 60 seconds.

Example:

"RATE-CB-1732454321-XYZ123"

metadata
object

Additional transaction metadata

Response

success
boolean
Example:

true

message
string
Example:

"Crypto bridge deposit initiated successfully."

data
object