On-Ramp & Off-Ramp

Introduction

This guide is for developers and product teams who want to understand and integrate IDR↔crypto ramps with KORAMP. KORAMP provides two directions:

• On-Ramp (Top Up): the user pays Indonesian Rupiah (IDR) and receives crypto to their wallet.
• Off-Ramp (Sell): the user sends crypto and receives IDR to their bank account.

KORAMP is wallet-first: no account required — a wallet address is the user's identity.

Field Visibility

The two tables below show the visibility level for each field in each direction.

Requirements

Before integrating, make sure you have:

1. An EVM or Solana wallet for the user, matching the selected asset.
2. A supported asset on a supported network (SOL, ETH, or BNB on testnet).
3. An IDR amount within the minimum and maximum limits for that asset.
4. The ability to sign messages to prove wallet ownership (EVM and Solana).
5. A callback endpoint or webhook to receive payment status notifications from the provider.

Assets and Inventory

1. SOL on Solana Devnet — Top Up and Sell ramp active. Account for the Associated Token Account (ATA) creation fee on recipient wallets that don't yet have an ATA.
2. ETH on Base Sepolia (chain 84532) — ramp active. EVM wallets need to add the Base Sepolia network if not already known.
3. BNB on BSC Testnet (chain 97) — ramp active. EVM wallets need to add the BSC Testnet network if not already known.

Compliance Considerations

Information You Can See

Information	On-chain	Off-chain
Sender address	Yes, public	Yes, public
Recipient address	Yes, public	Yes, public
Amount	Yes, public	Yes, public
Bank payout details	No	Last 4 digits only displayed
Wallet address in public ledger	Masked	Masked

Wallet Screening

KORAMP applies wallet screening as part of security operations. Current stance: screening focuses on abuse detection and rate limiting, not third-party compliance analytics. KORAMP does not claim coverage equivalent to dedicated compliance providers.

Travel Rule

KORAMP uses a KYC-less wallet-first model. As a result, classic Travel Rule mechanisms (collecting and exchanging sender/recipient data between institutions) are not available. This is adapted by maintaining an internal audit trail: no accounts, wallet-as-identity, and a publicly masked ledger.

Mapping Your Existing Flow

Existing step	KORAMP step
Send fiat	Pay via Xendit QRIS (scan and pay)
Receive crypto	Crypto sent to destination wallet
Sell crypto	Send to platform deposit address
Withdraw IDR	Fiat payout to bank via Xendit Payout v3

Records and Audit

Every significant transaction is recorded in the double-entry ledger and audit log:

Component	Function
AuditLog	Records important actions with actor and metadata.
LedgerEntry	Double-entry records (CREDIT/DEBIT) per wallet and asset.
XenditWebhook	Xendit webhook idempotency keyed on kind, event, paymentRequestId, and payoutId.

Transaction Flow

1. On-Ramp

1. User requests a TOP_UP quote.
2. Create a Top Up order and obtain a Xendit QRIS payment payload.
3. User scans the QRIS code and pays.
4. Xendit webhook notifies the server that payment succeeded.
5. Platform sends crypto to the destination wallet.
6. Order is marked complete when completedAt is set.

2. Off-Ramp

1. User requests a SELL quote.
2. Create a Sell order and obtain the platform deposit address.
3. User sends crypto to the deposit address.
4. Scheduler scans the deposit and tracks confirmations.
5. Once confirmations are sufficient, fiat payout is sent via Xendit Payout v3.
6. Order is marked complete when the payout succeeds.

Start Integrating

With an understanding of on-chain visibility and the flows above, you can start building a KORAMP ramp integration.