Keys
- Server side only. A request with a browser
Originis refused with403 KEY_IN_BROWSER. - One key per job: an order service with
usersandorders, a payout service withwithdraw. - Live Platform keys work only from IPs RekberPay approved.
A payment API for marketplaces in Indonesia. Your buyers and sellers stay on your site while RekberPay holds the money, runs the checkout, decides disputes and pays sellers out.
Sandbox from day one
Platform is on for every Enterprise workspace. Build with test money and a rpe_test_ key straight away. There is nothing to request.
Live after business verification
Once your KYB is approved and RekberPay approves the IP allowlist on your live key, real orders flow. See the path
RekberPay holds the money until the order is released. This link works for 30 minutes.
seller-2001Sample order from our sandbox walkthrough. Names and amounts are test data.
Wherever one of your users pays another for goods or services, and the money should wait until the buyer is happy.
The buyer pays at checkout, the seller ships, and you report the tracking number. The money releases when the buyer confirms, or on its own when the clock runs out.
One order can hold several milestones. Each is paid, delivered and released on its own, so a long job does not tie up the whole amount.
Your users never sign up with RekberPay first. Each one is still a real RekberPay user who can claim the account later, and ratings count on their public profile.
partner_user_refThat is not a marketplace order. Use B2B escrow for milestone deals with approvals, in the same workspace.
See B2B milestone escrowFrom checkout to the seller's bank, each step is a call you make or a signed webhook you receive.
Create a checkout link for the milestone and send the buyer there. The link works for 30 minutes.
POST …/checkoutRekberPay confirms the payment and holds it. Ask the seller to ship only after this event.
milestone.paidReport shipping. The buyer confirms, you confirm and it releases 6 hours later, or the clock runs out.
milestone.releasedThe seller's partner balance grows by the amount minus the seller's fee share. Show it in your app.
GET /users/:ref/balancePay out to a bank account whose holder name matches the seller, after a 24 hour cooling-off.
withdrawal.settledYou or the buyer can stop an order any time after payment. RekberPay's mediation team then releases, refunds, splits or resumes it, and a large decision needs a second approver. dispute.opened
Rate a finished order for the buyer or the seller. A rating stays private until both sides rate or 3 days pass, then counts on their RekberPay profile. rating.published
Every call needs read, plus write for changes and the scope shown on each group. Every write takes an Idempotency-Key.
Paths are under https://api.rekberpay.com/v1/enterprise/platform
orders:confirm, off by defaultusers)curl -s -X POST "$API/deals" "${auth[@]}" "${json[@]}" -H "$(idem)" -d '{
"buyer_ref": "buyer-1001",
"seller_ref": "seller-2001",
"title": "Fujifilm X-T30 body, used",
"partner_order_ref": "ORD-55012",
"milestones": [
{ "title": "Camera body", "amount": 4500000 }
],
"fee_bearer": "buyer"
}'{
"status": "awaiting_funding",
"platform_fee": 90000,
"milestones": [
{
"status": "awaiting_payment",
"funding_amount": 4590000,
"payout_amount": 4500000
}
]
}Build everything with test money first. Live needs two things: your business verified, and an IP allowlist on your live key that RekberPay approved.
It opens in Sandbox with Platform already on and the standard terms. There is nothing to request.
About ten minutes, with your company's NIBrpe_test_ keyIt works at once, from any IP. No email leaves RekberPay and no gateway is charged.
Four shortcuts pay, release, settle KYC and skip the cooling-offSend your KYB documents. Approval unlocks Live and turns Platform on there.
Reviewed in 1 to 3 business daysrpe_live_ keyEnter your server IPs on the key. Until RekberPay approves them, live calls answer 403 IP_ALLOWLIST_REQUIRED.
livemode: false.A Platform key can move your users' money, so RekberPay treats it like a bank password and enforces the rules for you.
Origin is refused with 403 KEY_IN_BROWSER.users and orders, a payout service with withdraw.Idempotency-Key, so a retry never opens a second order.404, never 403.The full answer to each is in the Platform mode guide and the Platform API reference. To compare both products, see the RekberPay Enterprise overview.
No. Your server creates their accounts with POST /users and they stay on your site. Someone who already has a RekberPay account is linked instead and confirms by email. Any user can claim their account later and use RekberPay directly.
The standard terms are a 2% fee per order with a Rp 5.000 minimum, paid by the buyer. You can set fee_bearer to buyer, seller or split per order. The payment method fee is added at checkout and paid by the buyer. Your account manager can change your terms, and GET /settings always shows them.
Only with the orders:confirm scope, which is off by default and must be allowed by RekberPay. Your confirm releases the money after 6 hours, and the buyer is told so they can still dispute.
RekberPay's mediation team. You or the buyer open the dispute and add evidence over the API. The team releases, refunds, splits or resumes the order, and you get a webhook with the outcome.
Your business verification approved, which unlocks Live, and a rpe_live_ key whose IP allowlist RekberPay approved. Your sandbox, its keys and its test orders stay as they are.
Yes. Platform mode sits next to B2B milestone deals in the same workspace, with the same team, keys, webhooks and sandbox. Use B2B escrow to pay your own suppliers, and the Platform API for orders between your users.
We built the whole flow against the sandbox first, then switched to live without changing our code. The signed webhooks line up with our own ledger, so reconciliation is boring now. Boring is exactly what you want with money.
Create a workspace, make a rpe_test_ key and take one order from checkout to withdrawal with test money. Go live when your business is verified.