API reference / Payments
/v1/captureAuthorise payment for an application
- Operation
capturePayment- Authentication
- API key
Authorise now, capture on government approval — the manual-capture model, because the decision is not ours to make.
Idempotent. Send an `Idempotency-Key` header; without one the application id and version are used, so a double-tapped button cannot create two authorisations. A replay returns the original result with `replayed: true` rather than charging again.
Scoped to the authenticated tenant. Keys issued to one tenant can never read or modify another tenant’s resources.
Request
Parameters
idempotency-keyheaderstringBody
application_idstringrequiredprovider_idstringrequiredreturn_urlstringrequiredlocalestringcheckout_reminder_requestedbooleanApplicant-requested single checkout reminder. Optional, never marketing consent.
Responses
payment_idstringrequiredstatusstringrequiredprovider_refstringnullrequiredreplayedbooleanTrue when the same idempotency key was seen before and the original result is being returned rather than charging twice.
errorobjectrequirederrorobjectrequirederrorobjectrequirederrorobjectrequiredExample
curl -X POST https://api.haavisa.com/v1/capture \
-H "Authorization: Bearer $HAAVISA_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"application_id": "<application_id>",
"provider_id": "<provider_id>",
"return_url": "<return_url>"
}'More in Payments
Something unclear? The eligibility guide explains the model behind the answers; the errors guide covers the envelope.