Keep money in scope
Bound the refund amount and currency. Reject caller-supplied beneficiaries, account overrides and independent arbitrary request bodies.
Give a refund workload the authority it needs—without turning payment-system access into an unlimited mandate.
The mapped refund operation binds the configured workload to a server-owned account and currency. The request supplies an original payment identifier and a positive integer amount in minor units.
Authorization evaluates refund.create against the account/payment resource and the meaningful business values that will be sent upstream.
Bound the refund amount and currency. Reject caller-supplied beneficiaries, account overrides and independent arbitrary request bodies.
Use the existing approval process when policy requires step-up authorization. Recheck the same inputs at release.
This illustrative HTTP request asks for a £45.00 refund when the reviewed adapter uses GBP minor units. Account selection and the target path belong to the server-owned mapping.
POST /v1/operations/refund/enforce
Authorization: Bearer <WORKLOAD_TOKEN>
Content-Type: application/json
{
"idempotency_key": "refund-order-001",
"inputs": {
"payment_id": "pay-1",
"amount_minor": 4500,
"currency": "GBP"
}
}Contract example · provision your own reviewed endpoint and credentials.
Confirm the original payment, account, currency and minor-unit interpretation with the protected system.
Attempt changed amounts, added fields, expired tickets, reused tickets and changed effective requests.
Validate TLS, credentials, network egress and the absence of a direct-upstream bypass.
Confirm that the approver sees the significant values and understands what will be released.
Define the actions, limits and approval process your team needs.
Let’s discuss your pilot