Skip to main content
PHP offramp lets your users convert their stablecoin balance into Philippine Pesos, settled to a bank account in the Philippines. Every offramp flow follows the same four steps: Create User → KYC → Bank Account Linkage → Transaction.
Both USDT and USDC are supported for PHP offramp.
1

Create User

Response:
Save user_id — every subsequent call needs it as the X-User-Id header.
2

KYC

PHP supports two KYC methods:
Headers: X-User-Id: <user_id>
Response:
Saber may request supporting KYC documents at any time — these must be shared within 72 hours of the request.
3

Bank Account Linkage

First, fetch the list of supported banks and their codes. This lookup only works for PHL — it returns an error for any other country:
data is a flat map of bank name to bank_code — pass the code as-is into bank_code below.
Headers: X-User-Id: <user_id>
For the Philippines, account_number (no spaces) and account_holder_name are required, plus at least one of bank_code or swift_code; bank_name is accepted alongside them.Response:
created_at/updated_at here are ISO 8601 date strings — unlike wallet-transaction endpoints, which use epoch milliseconds. Save bank_id for the sell step.
Unlike India, PHP bank accounts are approved instantly — there’s no penny-drop step.
A user can have up to 4 APPROVED bank accounts at any point in time (error 304012 when exceeded).
4

Transaction

Min ₱60 (~$1) per transaction; max depends on the user’s assigned limits (see User Limits & EDD below). payment_method: bank_transfer resolves internally to one of:
  • InstaPay — for amounts up to ₱50,000. Instant, no cut-offs. Banking fee: ₱8.
  • SwiftPay PESONet — for amounts above ₱50,000. T+1 settlement on working days. Banking fee: ₱4.
Two variants, both requiring a quote first — a Live Quote (informational, executes at market rate regardless) or a Locked Quote (rate held ~30-60s, supplied as quote_id in the sell request):

Checking status

Pool Sell:
External Sell:
Poll until the status reaches a terminal state, or configure a webhook URL to receive completion pushes instead — see Order Lifecycle and Webhooks.

User limits and EDD

Each user has a lifetime transaction limit (currently $200,000 USD equivalent — this figure is suggestive and subject to change; confirm current limits with Saber). Once a user’s limit is breached, no further transactions can be created until Enhanced Due Diligence (EDD) is completed to raise it. EDD is completed via the EDD Hosted Widget, with a turnaround time of 2-3 working days.

Offramp Operations

User KYC

Bank Account