Use Cases
Common use cases
Marketplaces for physical goods
Buyers pay up front and the money is held until the item arrives.
- Flow: the buyer presses "Checkout". You sign a link with
category: "goods"and create the escrow. - Timer: with a resi, the money is released 48 hours after the courier reports delivery, unless the buyer acts first. Without a resi, 72 hours after
sent. These are defaults andauto_completionon the escrow shows the real time.
Marketplaces that keep users on their own site
A marketplace where buyers and sellers never leave your product, with RekberPay holding the money behind it.
- Flow: your server creates RekberPay accounts for your buyers and sellers, opens an order with one or more milestones, and sends the buyer to a RekberPay checkout. You report shipping; the buyer confirms or the money is released automatically. Seller money lands in a balance you can pay out through the API.
- Product: Platform mode (PaaS), part of Enterprise. Start with Run a marketplace order end to end.
Freelance and service platforms
- Flow: the client accepts a proposal. You sign a link with
category: "service". - Timer: 36 hours after the freelancer marks the work delivered, unless the buyer acts first.
Digital goods
Accounts, game items, licences.
- Flow: a link with
category: "digital". - Timer: 36 hours after the seller marks it delivered.
Business deals with milestones
For companies that pay suppliers or partners in stages, use an Enterprise workspace. Six realistic setups are below, in Enterprise scenarios.
Enterprise scenarios
Every scenario here uses the same building blocks: a payer workspace that creates the deal and funds it, a counterparty that delivers and is paid, and milestones that are funded, delivered, approved and released one at a time. The names and amounts are made up. The platform fee in the examples is the default 2 percent of the deal total, and the four-eyes threshold is the default Rp 100.000.000 per milestone. Your own rate and threshold are in Settings. A deal is funded either in one payment up front (the dashboard default) or milestone by milestone (the default for a workspace API key); see Fund a live deal.
Pick the scenario closest to yours, then follow the guides it lists.
| Scenario | Payer | Counterparty | Fee | Key feature |
|---|---|---|---|---|
| Agency and client | The client | The agency | Split 50 / 50 | Design approval and revisions |
| Supplier and distributor | The distributor | The supplier | Payer pays | Four-eyes on large milestones, disputes on short delivery |
| Marketplace partner payouts | The marketplace | Each partner | Partner pays | API integration, split payouts, webhooks |
| Construction progress payments | The owner | The contractor | Split 50 / 50 | Retention milestone, due dates |
| Software outsourcing | The product company | The software house | Software house pays | Sprint milestones, revision requests |
| Event organizer and vendors | The organizer | Each vendor | Payer pays | Due dates, split payout to crew |
Agency and client
PT Maju Retail hires the agency PT Kreatif Pixel to build a website and a brand refresh for Rp 120.000.000. Both companies use RekberPay Enterprise.
- Who links to whom. Maju Retail (the payer) adds Kreatif Pixel as a counterparty and sends a link request with the agency's Workspace ID. An admin at the agency accepts it.
- Fee split. The agency offers to share the cost, so Maju Retail proposes Split 50 / 50. The fee is Rp 2.400.000, so each side carries Rp 1.200.000. The agency can accept or counter from Shared deals.
- Milestones.
| # | Milestone | Amount | Required evidence | Client funds | Agency receives |
|---|---|---|---|---|---|
| 1 | Kickoff and brief | Rp 36.000.000 | Signed brief | Rp 36.360.000 | Rp 35.640.000 |
| 2 | Design approved | Rp 48.000.000 | Figma link and approval email | Rp 48.480.000 | Rp 47.520.000 |
| 3 | Launch | Rp 36.000.000 | Production URL and handover notes | Rp 36.360.000 | Rp 35.640.000 |
- Approvals. Each milestone is below the threshold, so one finance approver is enough. If the client's team is unhappy with milestone 2, the approver chooses Request revision and the agency delivers again with the changes.
- Follow. Link a partner workspace, then Agree who pays the fee, then Run a deal in Sandbox, then in Live.
Supplier and distributor
PT Sumber Pangan buys 20 tonnes of rice from the supplier CV Tani Makmur on a purchase order of Rp 450.000.000.
- Who links to whom. The distributor is the payer. The supplier is a small business that does not use RekberPay, so it is a plain counterparty and nobody has to agree anything. The distributor's team records each delivery from the supplier's documents.
- Fee split. The distributor pays the whole fee, which is the default. The fee is Rp 9.000.000.
- Milestones.
| # | Milestone | Amount | Required evidence | Distributor funds |
|---|---|---|---|---|
| 1 | Deposit | Rp 135.000.000 | Signed purchase order | Rp 137.700.000 |
| 2 | Goods shipped | Rp 180.000.000 | Bill of lading and loading photos | Rp 183.600.000 |
| 3 | Goods received | Rp 135.000.000 | Goods received note and quality inspection | Rp 137.700.000 |
- Approvals. Every milestone is above the threshold, so each needs two different approvers. In Live, the person who recorded the delivery cannot approve it, so the finance director and a second finance approver decide.
- Disputes. If milestone 3 arrives 2 tonnes short, the distributor opens a dispute on it with the inspection report attached. RekberPay decides: the milestone goes back to funded so the supplier completes the delivery, it is released to the supplier, or it is cancelled.
- Follow. Add the supplier's payout account early, then Run a deal in Sandbox, then in Live, Four-eyes approvals and Disputes on a workspace deal.
Marketplace partner payouts
PT Pasar Nusantara runs a marketplace and settles each partner's sales every week, but only after its finance team has reconciled the sales report.
- Who links to whom. Each partner is a counterparty of the marketplace. Large partners that use RekberPay can be linked. Small merchants stay plain counterparties.
- Fee split. The marketplace passes the cost to the partner, so the deal uses Counterparty pays (
fee_allocation: "seller"). On a weekly batch of Rp 85.000.000 the fee is Rp 1.700.000 and the partner receives Rp 83.300.000. - Milestones. One deal per partner per month, one milestone per weekly batch. A deal holds up to 20 milestones, so a month of weekly batches fits easily. The required evidence is the reconciled sales report.
- Integration. The marketplace's backend creates the deal and its milestones with a workspace key and an
Idempotency-Key, pays each batch withPOST .../pay, submits the reconciliation report as evidence, and releases withsplitsto the partner's main account and its tax account (up to 5 accounts per release). A webhook endpoint listening formilestone.fundedanddisbursement.settledmarks batches paid in the marketplace's own ledger. With a linked partner the partner delivers the report from its own workspace instead, and it can choose the account it is paid to, so the marketplace releases with nosplits. - Follow. Enterprise quickstart, Fund a live deal, Releasing with split payouts and Receiving webhooks.
- Buyers pay, not the marketplace? When each order is paid by a shopper and released to a seller, use Platform mode (PaaS) instead of a workspace deal.
Construction progress payments
PT Griya Karya, a property owner, hires the contractor CV Bangun Mandiri to build a warehouse for Rp 2.000.000.000.
- Who links to whom. The owner is the payer. The contractor is linked, so it uploads progress evidence from its own Shared deals page.
- Fee split. Split 50 / 50. The fee is Rp 40.000.000, so each side carries Rp 20.000.000, spread over the milestones in proportion to their size.
- Milestones.
| # | Milestone | Amount | Required evidence | Owner funds | Contractor receives |
|---|---|---|---|---|---|
| 1 | Down payment | Rp 400.000.000 | Signed contract and bank guarantee | Rp 404.000.000 | Rp 396.000.000 |
| 2 | Foundation | Rp 500.000.000 | Progress photos and consultant inspection | Rp 505.000.000 | Rp 495.000.000 |
| 3 | Structure | Rp 500.000.000 | Progress photos and consultant inspection | Rp 505.000.000 | Rp 495.000.000 |
| 4 | Finishing | Rp 400.000.000 | Punch list signed off | Rp 404.000.000 | Rp 396.000.000 |
| 5 | Retention | Rp 200.000.000 | Handover certificate | Rp 202.000.000 | Rp 198.000.000 |
- Due dates. Set a due date on each milestone. The retention milestone's due date is 30 days after the planned handover. The owner funds it up front, and its approver approves it only once the contractor has delivered the handover certificate and the defect period has passed.
- Approvals. Every milestone is above the threshold, so each needs two approvers, for example the project finance lead and the director.
- Disputes. A structural defect found after milestone 3 is submitted can be disputed while the milestone is funded, submitted or approved.
- Follow. Link a partner workspace, Agree who pays the fee, Approve, release and settle.
Software outsourcing
PT Teknologi Lintas hires the software house PT Kode Karya to build a mobile app for Rp 300.000.000.
- Who links to whom. Both use RekberPay. The product company is the payer.
- Fee split. Kode Karya wants to win the contract and offers to carry the fee, so the deal uses Counterparty pays. The fee is Rp 6.000.000, held back from the payouts. The payer funds exactly the milestone amounts.
- Milestones.
| # | Milestone | Amount | Required evidence | Payer funds | Software house receives |
|---|---|---|---|---|---|
| 1 | Discovery and wireframes | Rp 60.000.000 | Wireframes and scope document | Rp 60.000.000 | Rp 58.800.000 |
| 2 | Sprint 1 and 2 | Rp 90.000.000 | Build link and test report | Rp 90.000.000 | Rp 88.200.000 |
| 3 | Sprint 3 and 4 | Rp 90.000.000 | Build link and test report | Rp 90.000.000 | Rp 88.200.000 |
| 4 | UAT and go-live | Rp 60.000.000 | UAT sign-off and store links | Rp 60.000.000 | Rp 58.800.000 |
- Approvals. Each milestone is below the threshold, so one approver decides. The person at the software house who delivers is not in the payer's workspace, so any approver of the product company can decide.
- Revisions. If UAT finds blocking bugs, the approver chooses Request revision with a note listing them. The software house fixes them and delivers again, and the review starts a new round.
- Follow. Link a partner workspace, Agree who pays the fee, Milestone deal end to end.
Event organizer and vendors
PT Gelora Acara organizes a conference and pays each vendor through its own deal. The sound and stage vendor, CV Suara Prima, is paid Rp 60.000.000.
- Who links to whom. The organizer is the payer. Vendors are counterparties. Vendors that already use RekberPay can be linked, the rest are plain counterparties.
- Fee split. The organizer pays the whole fee of Rp 1.200.000.
- Milestones. Use the event dates as due dates.
| # | Milestone | Amount | Due | Required evidence | Organizer funds |
|---|---|---|---|---|---|
| 1 | Deposit | Rp 18.000.000 | Signing | Signed vendor contract | Rp 18.360.000 |
| 2 | Setup complete | Rp 30.000.000 | Day before the event | Setup photos and sound check report | Rp 30.600.000 |
| 3 | Post-event | Rp 12.000.000 | After the event | Teardown report and equipment return | Rp 12.240.000 |
- Split payout. When releasing milestone 2 the finance team pays the vendor Rp 30.000.000 across two payout instructions, for example Rp 24.000.000 to the vendor's main account and Rp 6.000.000 to its crew account, in one release.
- Approvals. Each milestone is below the threshold, so one approver is enough. A vendor that does not show up for setup is disputed with Open dispute while the milestone is funded.
- Follow. Run a deal in Sandbox, then in Live, Approve, release and settle and Disputes on a workspace deal.
Before any of these goes live
- Create the workspace and invite your team.
- Verify your business, so Live unlocks.
- Rehearse the whole deal in Sandbox with test money. Sandbox stays open after Live unlocks.
- Add your live payout instructions early, because RekberPay verifies each one.
Example: Node.js backend
This Express handler signs a link, creates the escrow as the buyer and returns the checkout URL. It uses the buyer's API key, because the caller of POST /v1/escrows/from-link becomes the buyer.
import crypto from 'node:crypto';
import express from 'express';
const app = express();
app.use(express.json());
const BASE = 'https://api.rekberpay.com/v1';
const SECRET = process.env.LINK_SIGNING_SECRET;
const ALLOWED = ['amount', 'buyer', 'category', 'desc', 'expires', 'item', 'ref', 'seller', 'v'];
function canonicalString(params) {
return ALLOWED.filter((k) => params[k] !== undefined && params[k] !== '')
.map((k) => `${k}=${encodeURIComponent(String(params[k]))}`)
.join('&');
}
app.post('/checkout', async (req, res) => {
// In production, read the seller, item and amount from your own order
// record, not from the browser: the amount you sign is the price.
const { orderId, sellerId, item, amount, category, buyerApiKey } = req.body;
const params = {
seller: sellerId, // the seller's RekberPay user ID
item,
category, // goods, service or digital
ref: `ORDER_${orderId}`,
expires: Math.floor(Date.now() / 1000) + 24 * 60 * 60,
amount, // whole rupiah, signed with the rest
v: 1,
};
const canonical = canonicalString(params);
const sig = crypto.createHmac('sha256', SECRET).update(canonical).digest('hex');
const response = await fetch(`${BASE}/escrows/from-link`, {
method: 'POST',
headers: {
Authorization: `Bearer ${buyerApiKey}`,
'Content-Type': 'application/json',
'Idempotency-Key': crypto.randomUUID(),
},
body: JSON.stringify({ link: `https://rekberpay.com/?${canonical}&sig=${sig}` }),
});
const body = await response.json();
if (!response.ok) {
return res.status(response.status).json({ error: body.error.code });
}
res.json({ escrow_id: body.data.id, checkout_url: `https://rekberpay.com/escrow/${body.data.id}/pay` });
});
// Check the payment when the buyer comes back.
app.get('/orders/:escrowId/payment', async (req, res) => {
const response = await fetch(`${BASE}/escrows/${req.params.escrowId}/payment-status`, {
headers: { Authorization: `Bearer ${req.query.buyerApiKey}` },
});
const body = await response.json();
res.status(response.status).json(body);
});
app.listen(3000);Never send an API key from a browser. In a real system you keep the buyer's key on the server and look it up by session.