{
"event_type": "payin_settlement_scheduled",
"payin_id": "8b3e1c2d-4f5a-6b7c-8d9e-0f1a2b3c4d5e",
"account_id": "9b1deb4d-3b7d-4bad-9bdd-2b0d7b3dcb6d",
"country": "US",
"currency": "USD",
"local_amount": "498.75",
"fx_rate": "1.010202",
"usdt_gross": "493.811881",
"fee": "27.159654",
"usdt_net": "466.652227",
"status": "credited",
"settle_at": "2026-08-12T14:08:33Z",
"idempotency_key": "order-10042",
"receipt_url": "https://api.qbank.cl/platform/v1/payins/8b3e1c2d-4f5a-6b7c-8d9e-0f1a2b3c4d5e/receipt"
}Payin settlement scheduled
A card-paid payin — a direct card payin or a checkout/POS charge paid by card — was paid and its balance was scheduled for a future settle_at because your organization configured a settlement delay (settlement_hours) on the payin_card service. Emitted exactly once when the payment is confirmed (idempotent — a retry of the same confirmation does not re-emit it). status is credited from the start: the payin is confirmed and payin_credited fires right away — what waits until settle_at is only the BALANCE. usdt_net is the amount that lands when due (gross − fee); amount fields may come back empty ("") on historical rows without gross/fee. When settle_at is reached, the settlement worker releases the balance (the payin then carries settled_at instead of settlement_pending).
Every delivery includes X-Webhook-Event, X-Webhook-Event-ID, X-Webhook-Delivery-ID, X-Webhook-Timestamp and X-Webhook-Signature = hex(HMAC-SHA256(secret, timestamp + "." + body)). Respond 2xx; up to 5 attempts with incremental backoff.
{
"event_type": "payin_settlement_scheduled",
"payin_id": "8b3e1c2d-4f5a-6b7c-8d9e-0f1a2b3c4d5e",
"account_id": "9b1deb4d-3b7d-4bad-9bdd-2b0d7b3dcb6d",
"country": "US",
"currency": "USD",
"local_amount": "498.75",
"fx_rate": "1.010202",
"usdt_gross": "493.811881",
"fee": "27.159654",
"usdt_net": "466.652227",
"status": "credited",
"settle_at": "2026-08-12T14:08:33Z",
"idempotency_key": "order-10042",
"receipt_url": "https://api.qbank.cl/platform/v1/payins/8b3e1c2d-4f5a-6b7c-8d9e-0f1a2b3c4d5e/receipt"
}Authorizations
Session JWT (from register/login) or API key (pk_...).
X-API-Key: <token> is accepted as an alternative header.
Response
Return any 2xx to acknowledge the delivery.