resolveCancelRefund
Use the SDK for application integration. This read-only reference covers Commerce, Customer Auth, Membership and Events.
All HTTP operationsRequires an sk01_ write key. Managed refunds cannot be attested through this legacy caller-managed resolver; only the manifest-owned typed reason uses the strict Commerce envelope.
serverSecretKeyAuthorizationBearer <token>Public integration credential: opaque sk01_ secret API key only; PAT and Customer JWT are not supported by this scheme. Requires tenant binding and the read or write scope named by the operation.
X-Idempotency-Key*stringMust exactly match body idempotencyKey; reuse both for recovery.
1 <= lengthapplication/json- body
orderNumber*stringOrder number whose pending cancel refund is being resolved
1 <= lengthidempotencyKey*stringStable key for this PG refund result report
^[\x21-\x7E]+$1 <= length <= 255outcome*stringPG refund result reported by the storefront or BFF
"succeeded""failed"refundedAmount*integer0 <= value <= 9007199254740991pgProvider*string^[a-z0-9][a-z0-9_-]*$1 <= lengthpgRefundId?string1 <= lengthSuccessful operation
application/json- response
orderId*string1 <= lengthtransactionId*string1 <= lengthrefundTransactionId*string1 <= lengthrefundedAmount*integer0 < value <= 9007199254740991refundStatus*"succeeded""succeeded"transactionStatus*string"paid""refunded"Examples may be generated from schemas; they are illustrative, not recorded successful API calls. Example snippets may omit required authentication headers.
curl -X POST 'https://api.01.software/api/orders/resolve-cancel-refund' \ -H 'X-Idempotency-Key: string' \ -H 'Content-Type: application/json' \ -d '{ "orderNumber": "string", "idempotencyKey": "string", "outcome": "succeeded", "refundedAmount": 0, "pgProvider": "string"}'{ "orderId": "string", "transactionId": "string", "refundTransactionId": "string", "refundedAmount": 1, "refundStatus": "succeeded", "transactionStatus": "paid"}