Customer-funded mode

In customer_funded, the end customer pays the fee via a quoted rate with spread applied. The fee has two components: Ambar's operational margin (ambar_base_spread_bps) and the partner's commercial spread (org_spread_bps).

How it works

• The rate quoted to the end customer applies a total spread of ambar_base_spread_bps + org_spread_bps.
• On execution, Ambar captures the full margin via the rate.
• The ambar_base_spread_bps component is Ambar's direct operating margin and does not generate a ledger entry.
• The org_spread_bps component is a fee owed by Ambar to the organization. Per completed conversion, it is recorded as a ledger entry.
• Percentages are configured per direction: *_offramp and *_onramp are independent.

Worked example

Setup: mid = 1 USDT = R$ 5.00. Bob (end customer of organization Acme) offramps 100 USDT. Acme is on customer_funded with ambar_base_spread_bps_offramp = 100 (1%) and org_spread_bps_offramp = 150 (1.5%).

• Total spread on rate: 250 bps. Rate quoted to Bob: 5.00 × 0.975 = 4.875.
• Bob deposits 100 USDT, receives R$ 487.50.
• Ambar sells 100 USDT at a regulated exchange at mid, captures R$ 500.00. Captured margin: R$ 12.50.
• Decomposition: Ambar base = R$ 5.00 (1 USDT mid-equivalent, retained as operating margin, no ledger entry); partner spread = R$ 7.50 (1.5 USDT mid-equivalent, owed to the organization).
• Ledger entry on completion: { from=ambar, to=org, amount=1.50, currency=USDT, fee_kind=mode_b_org_spread }.
• Ambar later pays 1.5 USDT to Acme off-platform; the entry is marked settled.

How your organization sees it

The completed conversion exposes fee_mode='customer_funded', ambar_fee_bps, and org_spread_bps (the snapshotted percentages) in the payload. The target_amount in BRL already reflects the applied spread: it is the value effectively delivered to the end customer via Pix.

When this mode is appropriate

Typically when the organization wants to monetize the operation by charging the end customer through the rate, without billing separately in another flow. The end customer sees a worse-than-mid rate; the organization receives the spread share in periodic off-platform settlement.

Default configuration

ambar_base_spread_bps_offramp and ambar_base_spread_bps_onramp default to 100 bps (1%) per direction. org_spread_bps_* default to zero. Commercial negotiation can adjust any of them.

Next steps

• org_funded: the alternative in which the organization assumes the fee.
• Commercial settlement and internal ledger: how the payout is settled.