Announce a deposit you're expecting
Changed onRegisters an expected arrival before the money moves, and creates the PAY_IN transaction immediately at PENDING_FUNDS with settlement_status: FUNDS_EXPECTED. The transaction exists before the funds do.
What the intent means depends on the account it's against:
- On a PAYMENT-purpose account the intent is the locked order, and onUnder decides what happens if the payer sends less than expected.
- On a CONVERSION or BALANCE account it's an optional announcement.
The response carries an indicativeRate with binding: false. It's an indication, never a lock, and this endpoint accepts no quoteId.
Wait on deposit_intent.matched or deposit_intent.expired, then deposit.credited. See Webhooks and events.
Request
- Base URLhttps://api.sandbox.alfredpay.io
- URLhttps://api.sandbox.alfredpay.io/v1/customers/{customerId}/deposit_intents
- Auth
- HTTP bearer
- or API key in header api-key and API key in header api-secret
Headers
Required on every state-changing POST, simulators included; the only exempt POST is …/verifications/preflight. Replay (same key, same body) returns the original response with Idempotent-Replayed: true; same key with a different body → 409 idempotency_conflict. Keys are UUIDs, scoped to the API key, retained for 24 hours.
Request body
Example request
{
"expectedAmount": {
"value": "10000.00"
},
"tolerance": {
"underPct": "2.0",
"overPct": "5.0"
}
}Response
Created
Example response
{
"expectedAmount": {
"value": "10000.00"
}
}Changes
- info
endpoint added
- info