POST /api/v2/storefront/account-mappings/ready-to-invoice/{assertionId}/revoke
The reverse of asserting billing readiness,
and it fails closed: it immediately blocks new direct-billed activity on
the account (any active grant billed to this party moves to
payment_required), without touching buys already placed. It never falls
back to agent/Interchange billing on your behalf — that would put someone
else on the hook for an invoice you decided to send yourself.
Request
Parameters
Response
200 OK with the revoked assertion (state: "revoked"), in the same shape as
the assert response.
Errors
400 VALIDATION_ERROR—reasonis missing, empty, or too long.401 UNAUTHORIZED— missing or invalid API key.404 NOT_FOUND— no active assertion with this id under your storefront. An already-revoked assertion 404s the same way.
Related
Assert billing readiness
Confirm a direct-billed buyer is billable
Recover a billing-readiness assertion
Find the assertion id for an account that’s already active
Buyer Account Mapping
The review queue, whose
billingGate field reflects this state