Changelog
Every notable change that affects partners and users is listed here, one section per month, newest first. Items that start with Action needed ask you to change your integration. Subscribe to [email protected] for release emails.
November 2026
Rekber (escrow)
- A paid rekber can now be cancelled by agreement. The buyer or the seller asks, and if the other side agrees the rekber ends
refundedand the escrow amount goes back to the buyer's RekberPay balance. The payment fee and the unique code are not refunded. If the other side declines or does not answer in time, the rekber goes on and a dispute is still open to both sides. API:POST /v1/escrows/:id/cancel-request, answered with/acceptor/decline, and/withdrawfor the side that asked. The escrow read has a newcancel_requestfield. See Cancelling by agreement after payment and Ask to cancel a paid escrow. - Up to 5 files per chat or dispute message.
POST /v1/disputes/:id/messagestakes up to 5 URLs inevidence_urls(more answers400 INVALID_BODY).POST /v1/escrows/:id/messagestakes a newattachment_urlslist, up to 5 files in all withattachment_url. Message lists and sends addattachments(each file withurlandmime).attachment_url(andattachment_mimeon the dispute thread) stays the first file. POST /v1/escrows/:id/dispute,POST /v1/user/payout-accountsandPOST /v1/user/crypto-addressesaccept anIdempotency-Key. The saved payout account and crypto address routes now have reference pages in Withdrawals.
Payments
- Every manual bank transfer now carries a unique code of Rp1 to Rp999: rekber, Jasa Pembayaran, Rekber B2B deals and milestones, and the Platform checkout. The pay answer and the payment status add
pay_total(transfer exactly this, down to the last 3 digits) andunique_code.amountkeeps its meaning. The code is part of the transfer fee and is not refunded. - Action needed if your app shows its own manual bank transfer instructions: show
pay_totalinstead ofamount. A payer who sendsamountsends a little too little, and that payment takes longer to confirm. See the manual bank transfer guide and Pay a milestone (live).
Enterprise and Platform
- The CSV exports (
GET /v1/enterprise/reports/deals.csv,/reports/disbursements.csvand/audit/export.csv) take a new optionaltz=wib: every time is then written in WIB with the+07:00offset, the same instant. Without it nothing changes: times stay UTC withZ. The dashboard downloads usetz=wiband open in Excel with Indonesian text intact. See Export deals. - Platform chargeback deposit. When chargebacks in a month go over 1% of that month's volume, RekberPay asks for a deposit of 5% of the volume, paid in the dashboard within 7 days and returned once the ratio is back under control. It replaces the rolling reserve by agreement. A chargeback receivable is now due 14 days after it is recorded, and a past due one can be taken from the deposit. Four more events make 30 new webhook events for Platform in all:
deposit.required,deposit.paid,deposit.appliedanddeposit.returned. A webhook subscribed to*receives them: answer2xxto events you do not know. See Chargeback deposit and Platform webhook events. - Platform partner fee.
POST /v1/enterprise/platform/dealstakes a new optionalpartner_fee_bp(0 to 1000, 100 is 1%, default 0): your own commission on the deal, added to the RekberPay fee into one service fee that your buyers and sellers see as Biaya layanan. A value above the limit RekberPay set for your workspace (0 until you agree one) answers422 PARTNER_FEE_NOT_ALLOWED. Deals and milestones carry a newfeesblock (service_fee,rekberpay_fee,partner_fee), anddeal.created,milestone.paid,milestone.releasedandmilestone.auto_releasedadd the breakdown when the deal has a commission. The commission is credited at release and in a split, never in a refund, and settlement events carrypartner_commission.platform_fee,buyer_feeandseller_feestill mean the whole service fee, so nothing changes for an integration that ignores the commission. There are no commission webhook events. See Partner fee and commission. - New error
423 NEW_ORDERS_PAUSED. RekberPay can pause new Live orders for a workspace with an overdue deposit or receivable:POST /v1/enterprise/platform/dealsand a first payment on an order with nothing paid yet are refused, and everything else keeps working. Sandbox is never paused. See Pausing new Live orders. - Platform partners can decide their own disputes once RekberPay switches it on for the workspace:
POST /v1/enterprise/platform/deals/:id/milestones/:mid/dispute/resolvewithoutcome(release,refund,splitorresume),refund_amountfor a split, and anote. It needs theorders:confirmscope (afinance,adminorownermember) and answers403 PARTNER_DISPUTE_DISABLEDuntil switched on. New fieldpartner_resolves_disputes(off by default) inGET /settingsand intermsofGET /platform-status.dispute.resolvednow carriesdecided_by:rekberpayorpartner. See Decide a dispute. - The standard Platform fee is 2% per order with a Rp2.500 minimum (was Rp5.000).
GET /settingsshowsfee_min_idr: 2500unless you agreed other terms. Orders created before keep their fee. Rekber B2B deals keep the Rp5.000 minimum. GET /v1/enterprise/platform/deals/:idaddschat_openandchat_closes_at(30 days after the last release or refund,nullwhile a milestone is open or disputed). See Get a deal.POST /v1/enterprise/deals/:id/milestones/:mid/releaseanswers400 INVALID_BODYwhen twosplitsname the same payout account.POST /v1/enterprise/webhooks/:id/deliveries/:did/redeliveranswers409 DELIVERY_PENDINGwhile the same event is still being retried, so it never goes out twice. See Send a delivery again.- Notices that a deal was shared, activated or cancelled, or that a cancellation was answered or withdrawn, have their own type
enterprise_deal_updateand follow thedealsnotification toggle. - New activity feed events (not sent to webhooks):
deal.lead_changedandrequirement.removed. - Fixed:
PATCH /v1/enterprise/templates/:idreturns the storedupdated_at.
Apps and notifications
- RekberPay now has an official Telegram bot. Users get rekber updates there and can create, join, pay, ship, confirm, ask to cancel and open a dispute from a private chat or a Telegram group. Payments, balance and codes stay in the private chat. Users link it from Pengaturan > Notifikasi with Hubungkan Telegram. A step taken in Telegram lands on the same account and rekber, so the API shows the same status. The Telegram Bot page has the bot username to check against.
- In Pengaturan > Notifikasi each user picks which Rekber Status, Payment and Dispute updates also go out by email, WhatsApp or Telegram. In-app notifications always show. Nothing changes in the API.
Uploads
- When RekberPay is busy processing other uploads, an upload now answers
503 STORAGE_FAILEDwith aRetry-Afterheader (in seconds) instead of500. Nothing is wrong with the file: wait that long and send it again with a newIdempotency-Key. A real storage failure still answers500.
October 2026
Action needed
- Partner links:
amountis now a required signed field. The canonical order isamount,buyer,category,desc,expires,item,ref,seller,v.amountis whole rupiah as plain digits, 1000 to 500000000. Links signed without it fail with422 SIG_INCOMPLETE: addamount, sign again, and stop sending the price only in the body.POST /v1/escrows/from-linkneeds only{ "link" }. A bodyamount, if sent, must equal the signed amount (422 AMOUNT_MISMATCH). A signed amount out of range answers422 INVALID_AMOUNT, andamountwithoutsiganswersSIGNATURE_REQUIRED. See Authentication. - A signed link that names a
buyeris single use. A repeat call answers200 OKwith the escrow it already created andPartner-Link-Replay: true. Use a newrefper order. A link withoutbuyerstays reusable, at most 3 escrows per buyer and link every 10 minutes (429 LINK_USE_LIMITED).refover 64 characters answers422 INVALID_REF.expiresstays required and at most 30 days away. See Replay. - New email and password accounts must confirm their email. Until they do,
POST /v1/escrows,POST /v1/escrows/from-link,POST /v1/escrows/:id/join,POST /v1/escrows/:id/pay,POST /v1/escrows/:id/claim-payment,POST /v1/jasabayar,POST /v1/jasabayar/:id/pay,POST /v1/jasabayar/:id/claim-paymentandPOST /v1/withdrawalsanswer403 EMAIL_NOT_VERIFIED.GET /v1/auth/meaddsemail_verification_required. Existing accounts and Google sign-ups are not affected. POST /v1/escrows:amountmust be a whole number, andsource_urlmust be an http or https link (400 INVALID_BODYotherwise).- Accounts without KYC or an Akun Resmi badge have three escrow limits (per escrow, per rolling 24 hours, lifetime) on create, join and pay, on either side. New codes:
400 NONKYC_LIMIT_AMOUNT,429 NONKYC_LIMIT_DAILY,403 NONKYC_LIMIT_LIFETIME, and for signed links403 NONKYC_LIMIT_COUNTERPARTYand403 NONKYC_LIMIT_SELLER_AT_PAYMENT. Each refusal carries alimitsobject. See Limits for accounts without KYC. - Only the buyer pays.
POST /v1/escrows/:id/paytakes the empty buyer seat first (same checks as joining) and keeps it if the payment fails.403 NOT_BUYERanswers when someone else holds the buyer seat. - Withdrawals need a verified KYC:
POST /v1/withdrawals,POST /v1/enterprise/platform/users/:ref/withdrawalsand a person's own partner balance withdrawal answer403 KYC_REQUIREDotherwise. A bank account holder who is not the KYC name answers422 NAME_MISMATCH. Nothing is debited, and withdrawals already pending go on. POST /v1/withdrawalswithmethod: "bank_transfer"and nobank_codemust name a listed bank inbank_name(400 BANK_CODE_REQUIRED). Sendbank_code(otherfor an unlisted bank).- Payment status reads (
GET /v1/escrows/:id/payment-status,GET /v1/jasabayar/:id/payment-statusand the enterprise ones) no longer sendraw_response. The enterprise reads addbank_nameandaccount_holderfor a manual bank transfer. - Enterprise workspace keys (
rpe_) are refused from browsers: a request with a browserOriginorSec-Fetch-Siteheader answers403 KEY_IN_BROWSER. Move such calls to your server. A request from a website RekberPay does not allow answers403 ORIGIN_NOT_ALLOWEDinstead of500. - Live Platform keys need an IP allowlist approved by RekberPay, otherwise
403 IP_ALLOWLIST_REQUIRED. Existing Platform keys with a list wait for approval before they work in Live. See Going live: get your IPs approved. - Enterprise release splits must add up to the milestone
payout_amount(the amount minus the counterparty fee share). - Platform chat needs the new
messagesscope. Keys made before it was added do not have it, so make a new key. - Deprecated:
is_sandboxon enterprise reads is a copy ofmode === "sandbox"and will be removed in a later release.
Rekber (escrow)
POST /v1/escrows/:id/cancel(andPATCH /v1/escrows/:id/statuswithcancel) answers409 PAYMENT_IN_PROGRESSwhile a payment is still open.POST /v1/escrows/:id/sendandPOST /v1/escrows/:id/trackingrefuse a tracking number already on another live escrow (409 AWB_IN_USE) or recorded by the courier before payment (409 AWB_PREDATES_PAYMENT). The same buyer and seller may share one number for combined shipping.- A party sees only their own email:
buyer_email,seller_emailandsender_emailarenullfor the other party in escrow, preview, message and dispute reads. New fieldcounterparty_username. Invite emails are capped per recipient and per sender. GET /v1/escrows/:id/messagesandGET /v1/disputes/:id/messagesacceptafter_idnext toafter, so two messages in the same millisecond are never missed.- Loyalty discounts and one-time fee vouchers now apply: the escrow fee at release, the withdrawal fee at
POST /v1/withdrawals. A voucher comes back if the withdrawal is rejected or the release is reversed.GET /v1/escrows/fee-estimateandGET /v1/escrows/:id/fee-previewaddfee_before_discount,loyalty_discount_percent,loyalty_discount_idr,voucher_codeandvoucher_discount_idr.GET /v1/withdrawals/configaddswithdraw_fee_loyalty_discount_percentandwithdraw_fee_vouchers. GET /v1/escrows/:id/fee-previewis for the seller only (403 FORBIDDENfor the buyer).POST /v1/escrows/:id/paycan answer409 ESCROW_ALREADY_PAID.- Suspended accounts stay on the public directory and profile with a warning.
GET /v1/public/users,GET /v1/public/users/:usernameand Platform reputation addsuspended,fraud_flagged,fraud_flagged_atandaccount_status(active,suspendedorfraud_flagged). A new rekber, join, payment or signed link with such a counterparty answers409 COUNTERPARTY_SUSPENDED.GET /v1/escrows/:id/previewaddsbuyer_account_statusandseller_account_status, andrater_is_verifiedisfalsefor such a rater. See Account status. - Public profiles under
/v1/publicmay be served from a cache up to 60 seconds old.
Payments and withdrawals
- New payment method
cstore: pay a code in cash at an Alfamart or Indomaret cashier, where offered.GET /v1/gateways/available-methodslists it withcstore_channelsandcstore_store_fees. Pay requests send the store aschannel(400 INVALID_CHANNEL,400 UNSUPPORTED_METHOD). The payer total must be Rp10.000 to Rp5.000.000, store fee included (400 AMOUNT_OUT_OF_RANGE). The code is inva_number, the store inva_bank, pluspayment_nameandstore_fee. Funded milestones carryfunding_method: "cstore". GET /v1/gateways/available-methodstakesamountandkind(escrow,jasabayar,enterprise) and returns the method fee for that amount. A workspace key cannot call it. QRIS buyer fees are listed there with the other method fees.- A DANA or GoPay number that is not the user's own is accepted, but the withdrawal starts in
pending_reviewand waits at least 24 hours. Readstatusfrom the answer. - Crypto withdrawals go only to a saved address that was confirmed by email and has waited 24 hours, matched exactly (
403 CRYPTO_ADDRESS_NOT_ACTIVE). They are capped per 24 hours, Rp10.000.000 by default (400 CRYPTO_DAILY_LIMIT), and always start inpending_review. - KYC submit answers
409 NIK_IN_USEwhen the NIK already verifies another account, including a deleted one whose KYC was verified. - The default minimum withdrawal is Rp10.000 (was Rp50.000). Below it the answer is still
422 INVALID_AMOUNTwithlimits.min_idr, and the whole balance can still be taken out. - A completed withdrawal the bank sends back is marked
returnedand the whole amount, fee included, goes back to the balance. Platform webhookwithdrawal.returnedhas the same fields aswithdrawal.failed. - The withdrawal fee quoted by
GET /v1/withdrawals/configis now the feePOST /v1/withdrawalscharges.
Account and security
- New personal API keys start with
rpk_. Older keys keep working until rotated.POST /v1/auth/me/api-key/rotateallows 5 rotations per hour (429 ROTATE_LIMITED), checkslabel(up to 64 letters, digits, spaces or_ . : -) and emails the owner on every rotation, without the key. Signing in on the phone apps no longer changes the key.GET /v1/auth/me/api-keyshows only the active key (nullwhen none) withcreated_atandlast_used_at. - A password reset or change revokes every personal API key. Create a new one afterwards.
Idempotency-Keyis scoped to the exact path, the API key and the enterprise workspace as well as the user.GETrequests ignore it.- Uploads are checked from their first bytes, images lose EXIF data, PDFs are cleaned of scripts and attached files, and only the uploader can attach a file, once.
POST /v1/upload/:typereturnsupload_id,mime,sizeandsha256, honoursIdempotency-Key, allows 40 uploads per 10 minutes and has a daily quota. New codes replaceINVALID_MIME,INVALID_FILE_TYPEandUPLOAD_FAILED:FILE_EMPTY,413 FILE_TOO_LARGE,TYPE_NOT_ALLOWED,TYPE_MISMATCH,POLYGLOT,IMAGE_TOO_LARGE,IMAGE_DECODE_FAILED,PDF_PASSWORD_PROTECTED,PDF_DAMAGED,PDF_TOO_MANY_PAGES,PDF_UNSUPPORTED_ENCODING,PDF_ACTIVE_CONTENT,PDF_EMBEDDED_FILE,429 QUOTA_EXCEEDED,500 STORAGE_FAILEDand503 PDF_CHECK_UNAVAILABLE(try again in a few minutes). Attaching can fail withUPLOAD_INVALID_REF,UPLOAD_NOT_FOUND,UPLOAD_NOT_OWNED,UPLOAD_WRONG_PURPOSE,409 UPLOAD_ALREADY_BOUNDor409 UPLOAD_QUOTA. Errors carrymessage_idandmessage_en(sendX-RekberPay-Lang: en). File links are bound to the person they were issued to. - The
userobject on every auth response addscreated_at(ISO 8601 UTC). - Signed-in users can read and answer their own support tickets:
GET /v1/support/tickets,GET /v1/support/tickets/:idandPOST /v1/support/tickets/:id/replies(2 to 5000 characters,400 INVALID_REPLY, 8 replies per 15 minutes, honoursIdempotency-Key).statusisclosed,repliedorawaiting_admin. A reply from RekberPay support sends asupport_replynotification withmetadata.ticket_id. GET /v1/notifications/streamsends the unread notification count as server-sent events. See Notifications.
Enterprise (Rekber B2B)
- The enterprise dashboard is at
https://enterprise.rekberpay.com/dashboard, with its API under/v1/enterprise: workspace, members, counterparties, deals and milestones, approvals, payouts, documents, the event feed, reconciliation, reports, templates (up to 50), deal notes, notifications and the audit CSV (financerole and up). Workspace keys (rpe_) have thereadorreadandwritescopes. Keys get403 KEY_NOT_ALLOWEDon dashboard-only routes and403 SCOPE_REQUIREDon writes withoutwrite. See the Enterprise reference. - Signed webhooks: up to 10 HTTPS endpoints per mode,
X-RekberPay-Signature: t=<unix>,v1=<HMAC-SHA256 hex>over<t>.<raw body>, retries after 1m, 5m, 30m, 2h and 12h, paused after 20 failed attempts in a row. A webhook subscribed to*receives every event, so answer2xxto events you do not know. See Webhooks and Handling webhooks. - Self-serve sign-up with
POST /v1/enterprise/registerand business verification (KYB) under/v1/enterprise/kyb, plus counterparty verification links (POST /v1/enterprise/counterparties/:id/kyb-invite, which takes{ "send_email": true }, and/v1/kyb/invite/:token). NIK, passport and bank account numbers are encrypted and never returned in full, and KYB data is kept for 5 years after the relationship ends. A flagged document cannot be replaced by the same file (409 SAME_FILE), a resubmit with nothing changed answers422 NOTHING_CHANGED, and the bank holder must match the legal name or be confirmed withbank.holder_confirmed: true. Other codes:503 KYB_UNAVAILABLE,500 KYB_SEAL_ERROR. See Verify your business. - Sandbox and Live in one workspace. Sandbox (test money) is open from day one, and Live unlocks when your KYB is approved. Nothing in Sandbox is cancelled when Live unlocks, and Sandbox never changes Live. New keys start with
rpe_test_orrpe_live_(olderrpe_keys keep their mode). A session or personal key picks the mode withX-Enterprise-Mode: sandboxorlive. Data of the other mode answers404 NOT_FOUND. Keys and webhooks are limited to 10 per mode./me,/settingsand/kybaddmodeandlive_unlocked, every event and webhook carrieslivemode, and test rows carryis_test: true. See Testing in Sandbox and Sandbox and Live keys. - Mode error codes:
400 INVALID_MODE,403 LIVE_LOCKED,403 KEY_MODE_MISMATCH,409 COUNTERPARTY_LIVE_LOCKED(replacesMODE_MISMATCH),409 LINK_HAS_LIVE_DEALS,409 COUNTERPARTY_HAS_LIVE_DEALS,409 COUNTERPARTY_LIVE_VERIFIED,409 LIVE_SETTING_SANDBOX,409 LIVE_DEAL_IN_SANDBOX,409 TEST_DEALand409 SANDBOX_WORKSPACE. Sandbox emails go to members only with a[Sandbox]tag, and a disputed Sandbox deal can be released as a simulation. - Every enterprise deal pays a platform fee: 2% of the deal total, at least Rp5.000, or your agreed pricing.
POSTandPATCH /v1/enterprise/dealstakefee_allocationandfee_buyer_percent. Deals carrydeal.feeand, per milestone,buyer_fee,seller_fee,funding_amountandpayout_amount. New:GET /v1/enterprise/feesandPOST /v1/enterprise/fees/preview(needswrite). See Enterprise platform fee. - Linked workspaces: a counterparty can be linked to the RekberPay workspace behind it, with consent from both sides, by Workspace ID. New routes
POST /v1/enterprise/counterparties/:id/link,GET /v1/enterprise/counterparty-links,POST /v1/enterprise/counterparty-links/:id/acceptand/decline,DELETE /v1/enterprise/counterparties/:id/link,POST /v1/enterprise/counterparty-links/:id/unlinkandPOST /v1/enterprise/counterparties/:id/use-as-regular. Ending a link never takes rights away mid-deal (409 DEAL_ARCHIVED,409 COUNTERPARTY_UNLINKED). See Linked workspaces. - The linked workspace works on shared deals under
/v1/enterprise/shared-deals: read, deliver, dispute, answer a dispute and agree the fee. It never sees the payer's private data. On a deal with a linked counterparty the fee split is a proposal (deal.fee_agreement), and activation answers409 FEE_NOT_AGREEDuntil it is agreed. New eventsdeal.fee_proposed,deal.fee_agreed,counterparty.link_requested,counterparty.linked,counterparty.link_declinedandcounterparty.unlinked. See Fee agreement. - The deal room: a counterparty without a workspace gets a read-only preview link when a live deal is activated and can link its own workspace from there. Both sides then share next steps, a milestone tracker, files, document requirements, a timeline and messages (append-only, 20 posts a minute per user, 200 a day per deal,
429 MESSAGE_LIMIT_REACHED). Live counterparty writes need approved KYB (403 KYB_REQUIRED). Routes answer404until the deal room is on for your workspace;GET /v1/enterprise/mesays so indeal_room_enabled. See Enterprise deal room and Share a deal with your counterparty. - Live milestone funding:
POST /v1/enterprise/deals/:id/milestones/:mid/pay,GET .../payment-statusandPOST .../claim-paymentfor a manual transfer. Deals also havefunding_mode:upfront(one payment for the whole deal) orper_milestone. API-key deals default toper_milestone, so existing integrations are unchanged. New whole-deal routes/pay,/payment-status,/claim-paymentand Sandbox/fund. New codes409 FUNDING_MODE_LOCKED,409 FUND_WHOLE_DEAL,409 DEAL_NOT_ACTIVE(funding a draft) and409 LIVE_FUNDING_IS_PLATFORM_CONFIRMED.deal.fundedis now a webhook event. See Funding a live milestone and Funding a deal upfront. - Finance can cancel a funded deal: alone before the counterparty joined with a workspace, by agreement after (
202withstatus: "cancel_proposed", 7 days to confirm or decline).409 PAYMENT_IN_PROGRESSwhile a payment can still land. - When a dispute cancels a funded milestone, your workspace is refunded the
amountplus thebuyer_feeshare you funded. Deals addrefunded_amount,refund_pending_amountand a per-milestonerefund. New webhooksrefund.queued,refund.requeued,refund.processing,refund.settledandrefund.failed. A large dispute decision or refund can take a little longer, and the milestone staysdisputeduntil then. See Refunds. - A live release to a counterparty without business verification answers
409 COUNTERPARTY_KYB_REQUIREDand the money stays held.deal.payout_kybandproposed.payout_kybsay in advance whether a release would pass. On a shared deal only the counterparty delivers (409 PAYEE_DELIVERS), and release takes nosplitswhen it chose its payout account (409 PAYEE_CHOSE_PAYOUT). A payoutaccount_holdermust be the verified company name (422 BANK_NAME_MISMATCH). See Holder name. - Approvals:
409 SUBMITTER_CANNOT_APPROVEapplies in Live only. NewGET /v1/enterprise/approvals/second-approver?amount=andGET /v1/enterprise/approvals?status=ready. - Colliding writes answer a retryable
409 CONCURRENT_MODIFICATIONinstead of500.POST /v1/enterprise/counterpartiesanswers409 DUPLICATE_COUNTERPARTYfor an existing company name unless you sendallow_duplicate: true. Counterparties and documents accept anIdempotency-Key. Disputes takedocument_idsand evidence while open (409 NOT_DISPUTEDafter). - Workspace keys take
allowed_ips(up to 20 IPs or CIDR ranges,401 KEY_IP_NOT_ALLOWEDfrom elsewhere). Workspace admins can change the list in Developers. Platform key lists go to RekberPay for review (allowed_ips_status). Removing a member revokes the keys they created (status: "inactive"). - Invites from Sandbox workspaces are emailed.
resend-inviteworks once every 10 minutes (429 RESEND_TOO_SOONwithRetry-After) and answersemail_sent: trueor502 EMAIL_NOT_SENT. - Help in the dashboard menu opens how-to guides, use cases and a getting-started checklist.
Platform mode (PaaS)
- Marketplaces can run RekberPay escrow behind their own product under
/v1/enterprise/platform: create and link users, open marketplace deals with milestones, send buyers to a RekberPay checkout, report shipping, confirm receipt, follow disputes, read balances and pay users out. Platform is on for every workspace with the standard terms (2% fee paid by the buyer, 6 hour confirm delay, every scope butorders:confirm). Start with Platform mode (PaaS) and the Platform reference. - New key scopes
users,kyc,orders,orders:confirm,balance:read,withdraw,ratingsandmessages. Every Platform write with a workspace key needs anIdempotency-Key(400 IDEMPOTENCY_KEY_REQUIRED). A cut-short order action can be sent again with the same key. See Platform scopes. GET /v1/enterprise/platform-statusreads the Platform state of both modes, your terms and today's usage. See Get the Platform status.- Webhook events:
platform.user.linked,platform.user.consent_declined,platform.user.claimed,platform.user.unlinked,platform.user.kyc_updated,platform.user.balance_scope_changed,platform.user.deletion_requested,platform.user.deletion_cancelled,platform.user.deleted,bank_account.added,milestone.paid,milestone.shipped,milestone.received,milestone.release_pending,milestone.auto_released,milestone.auto_refunded,milestone.extended,milestone.release_reversed,message.created,withdrawal.requested,withdrawal.settled,withdrawal.failed,withdrawal.returned,rating.created,rating.publishedandrating.hidden.*also receivesdispute.evidence_added.dispute.resolvedfor a refund or split carriesrefund_amount,buyer_fee_refundedandbuyer_credit. See Platform webhook events. - Deal chat, tracking and invoices: list, post, mark read and attach (JPG, PNG, WebP or PDF up to 5 MB, five per message, 20 messages a minute per side, 200 a day per deal). Chat closes 30 days after the last release or refund unless a dispute is open (
409 DEAL_CLOSED_FOR_CHAT). Partners post withas: "partner", andauthorisbuyer,seller,partnerorrekberpay. NewGET .../deals/:id/invoiceandGET .../milestones/:mid/tracking. Unclaimed buyers and sellers get a secure emailed link to the deal (valid 7 days) and their messages arrive withsource: "link". See Deal chat. - Buyers can pay from their partner balance, signed in on the web or from the secure deal link (Bayar pakai saldo), with no payment method fee:
milestone.paidcarriesfunding_method: "balance"andpayment_method_fee: 0.deal_link_balance_paymentin settings turns the deal link option off on request. New codes403 BALANCE_PAYMENT_DISABLED,409 ORDER_CHANGED,403 WEB_SESSION_REQUIRED,403 NOT_BUYERand409 INSUFFICIENT_BALANCE. See Paying from the partner balance. - The invoice can carry your branding:
partner { name, logo_url, note }, set in dashboard Settings and shown asinvoice_branding. See Brand the invoice. - Ship refuses a reused tracking number (
409 AWB_IN_USE,409 AWB_PREDATES_PAYMENT) and takesproof_attachment_ids(up to 5,422 ATTACHMENT_INVALID), posted to the chat as proof of shipment. See Tracking numbers that were used before. - A paid milestone the seller never ships is refunded to the buyer's partner balance after the no-ship window, once it is switched on for you (
milestone.auto_refunded). A ship after that answers409 INVALID_STATE. See Milestone timers. - Chargebacks after release send
milestone.release_reversedwithamount,recovered_amount,receivable_amount,settlement,buyer_recovered_amountandseller_recovered_amount. RekberPay recovers from the partner balances first, and your workspace owes the rest. See Chargebacks after release. - Account deletion:
POST,GETandDELETE/v1/enterprise/platform/users/:ref/deletion. An unclaimed account enters a 30 day waiting period and can be cancelled until it is anonymised. An account the person controls is never deleted on your word: the answer isuser_confirmation_required. Codes409 DELETION_BLOCKED(includingOPEN_RECEIVABLE) and409 DELETION_NOT_CANCELLABLE. See Request account deletion. - Withdrawals pay one flat fee by bank rail:
bifastRp4.000 by default for an accepted bank code,online_transferRp8.000 otherwise, and the e-wallet fee for an e-wallet code. The answer addsfee_rail, andGET /v1/enterprise/platform-statusadds the rail fees. A payout bankholder_namemust be the user's KYC name (422 NAME_MISMATCH). The whole partner balance can always be withdrawn, even under the minimum. See Withdrawal fees. - Non-KYC limits count a milestone from checkout or payment, one place per order (
422 LIMIT_EXCEEDED,409 PAYMENT_IN_PROGRESS). Ratings on marketplace deals share one reputation across RekberPay, and public reviews gainvia_partner. See Ratings. - Connect emails are limited to about 3 a day per person (
429 MAIL_LIMIT_REACHED). Sandbox shortcutssimulate/advance-timeandbank-accounts/:id/simulate/skip-cooling-offanswer404in Live.
Docs
- Every public endpoint now has its own reference section with auth, rate limit, idempotency, samples in curl, Node.js, Python and PHP, a real response and every error code. The public base URL is
https://api.rekberpay.com/v1. - New guides: Authentication and API keys, Payments and checking status, Handling disputes, Jasa Pembayaran orders, Enterprise quickstart, Milestone deal end to end, Four-eyes approvals, Releasing with split payouts, Polling events, Errors and rate limits, Keep notes on a deal, Reuse deal templates, Invite a company to link workspaces and Notifications and reminders.
- Corrections: ratings, disputes, documents, counterparties, members and settings do not use
Idempotency-Key.POST /v1/escrows/:id/confirmreleases in the same call. Signature and link failures answer422(SIG_MISMATCH,LINK_EXPIRED,HOST_NOT_ALLOWED), andINVALID_SIGNATUREandDUPLICATE_REFare not returned.POST /v1/enterprise/counterpartiesrequirescountry_code. Deal events are returned oldest first.
August 2026
- Jasa Pembayaran is documented:
GET /v1/jasabayar/config,POST /v1/jasabayar/quote,POST /v1/jasabayar,GET /v1/jasabayar,GET /v1/jasabayar/:idandPOST /v1/jasabayar/:id/cancel. An order is not an escrow and has its own status enum (awaiting_payment,pending_review,paid,processing,delivered,refunded,cancelled). An order not delivered within its SLA is refunded in full automatically (auto_refunded). - The default escrow fee is 1% with a Rp2.500 minimum, RekberPay's published rate. The fee you are charged is always the one the fee preview returns.
POST /v1/escrows/:id/extendlets a buyer push backauto_release_at(409 EXTEND_LIMIT_REACHED,409 EXTEND_DISABLED).POST /v1/withdrawalsacceptsdestination_ack: true. Money sent correctly to a destination the user mistyped is not refundable, and this record shows the user confirmed it.- Fixed: retrying
POST /v1/ppob/checkoutorPOST /v1/vouchers/redeemwith the sameIdempotency-Keyreplays the first result instead of answering409 IDEMPOTENCY_KEY_IN_FLIGHT. - Corrected: the docs described outbound webhooks for escrows that never existed. That was our mistake. Consumer escrows and Jasa Pembayaran orders still do not send webhooks: poll
GET /v1/escrows/:id/payment-status,GET /v1/jasabayar/:id/payment-statusorGET /v1/escrows/:id(every 5 to 10 seconds is well inside the rate limit). Enterprise webhooks arrived in October. - Corrected: bearer API keys (
Authorization: Bearer <api-key>) have always worked, issued atGET /v1/auth/me/api-keyand rotated atPOST /v1/auth/me/api-key/rotate. Rotation revokes all existing keys at once and returns the new key once. Bearer callers need no CSRF token; cookie sessions still sendX-CSRF-Tokenon writes. - Corrected: not every write honours
Idempotency-Key. The idempotency guide lists which routes do. The real codes are422 IDEMPOTENCY_KEY_CONFLICTand409 IDEMPOTENCY_KEY_IN_FLIGHT(retry with the same key).LINK_EXPIREDandSELLER_NOT_FOUNDare422,GATEWAY_TIMEOUTis502 GATEWAY_ERROR, and a body that is too large answersFST_ERR_CTP_BODY_TOO_LARGE.INVALID_VERSION,MISSING_FIELDandDUPLICATE_REFare never returned.
July 2026
attachment_urlvalues in chat, dispute evidence and escrow attachments are short-lived signed links (?exp=…&sig=…, valid roughly 12 to 24 hours). Use them as returned and read the parent again for a fresh link. Uploads still return a bare URL to submit back as before.POST /v1/escrows/from-linkrequires a valid HMAC signature whenever partner parameters are present (400 SIGNATURE_REQUIRED). Malformed URL encoding answers400instead of500.- Fixed: a confirmed payment is no longer missed after a temporary error, and a late
expiredorfailedupdate can no longer overwrite apaidpayment.
June 2026
- Sellers can add a courier and tracking number (resi) when marking an escrow shipped:
POST /v1/escrows/:id/sendtakes{ courier, tracking_number }. NewGET /v1/escrows/:id/trackingandPOST /v1/escrows/:id/tracking/refresh(once per escrow every 5 minutes).GET /v1/escrows/:idincludes atrackingobject with a link to the courier's official tracking page. - Cryptocurrency payments.
- Payment methods can carry a surcharge (
fee_percentandfee_fixed), shown inGET /v1/gateways/available-methodsandPOST /v1/escrows/:id/pay. Payment responses addescrow_amountandsurcharge. - Fixed: a failed request (any non-2xx) is no longer stored against its
Idempotency-Key, so a retry with the same key runs again. Successful answers are still replayed.
May 2026
- First public release of the API and the docs.
POST /v1/escrows/from-linkfor HMAC-signed partner links.GET /v1/escrows/:id/preview, a public preview of an escrow.GET /v1/escrows/:id/payment-statusto poll for a payment.Idempotency-Keyheader on write endpoints (see the August corrections for which ones).- Default fee 3% with a Rp5.000 minimum (was 2.5% and Rp3.000), later replaced by 1% with a Rp2.500 minimum in August.
Stability promise
We commit to no breaking changes within signature version v=1, the current version. Any breaking change will:
- Bump the version (
v=2) and ship alongsidev=1 - Be announced 90 days before
v=1is deprecated - Be 180 days before
v=1is removed
Additive changes (new fields, new events, new endpoints) are not breaking and will be released without a version bump.
New enum values (a new status, code, author or author_side, a new event type) and new response fields are additive too. Write your client to accept a value or field it does not know: ignore an unknown field, show an unknown enum value as a neutral label, and treat an unknown error code by its HTTP status. Never fail a request or drop a webhook because of one.
We broke this promise once: in October 2026 amount became a required signed field of the partner link while the version stayed v=1. The October section has the upgrade steps.