confirmLegacyPayment
Use the SDK for application integration. This read-only reference covers Commerce, Customer Auth, Membership and Events.
All HTTP operationssk01_ write only; PAT/customer/session denied. Provider-finality policy still applies; caller evidence is not a generic financial bypass.
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?stringOptional retry identity. Preserve exact body and identity for the same operation; absence does not imply safe automatic retry.
1 <= lengthapplication/json- body
orderNumber?string1 <= lengthcheckoutToken?string1 <= lengthpgPaymentId*string1 <= lengthpgProvider*string^[a-z0-9][a-z0-9_-]{0,63}$pgOrderId?string1 <= lengthamount*integer0 <= value <= 9007199254740991currency?string1 <= lengthpaymentMethod?stringreceiptUrl?stringuriapprovedAt?stringproviderStatus?stringproviderEventId?string1 <= lengthconfirmationSource?string"provider_webhook""provider_lookup""provider_api_confirm""manual_server"paymentKey?string1 <= lengthmetadata?Actual shaped success body
application/json- response
orderId*string1 <= lengthtransactionId*string1 <= lengthstatus*"paid""paid"alreadyConfirmed?booleanExamples 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/confirm-payment' \ -H 'Content-Type: application/json' \ -d '{ "pgPaymentId": "string", "pgProvider": "string", "amount": 0}'{ "orderId": "string", "transactionId": "string", "status": "paid", "alreadyConfirmed": true}