RecurringBillingSkipCategory
A model the API reference uses in a request or a response. The operation pages link every field typed as this model here.
Why a recurring billing run did not charge a contract that was due. Recorded on the run item for every skip and on the contract's `lastBillingSkip` for every skip someone can act on.
Values
Values:
Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
AlreadyBilled |
The contract already has a successful charge for this scheduled run. Harmless: nothing is owed, and nothing needs attention. |
MerchantIneligible |
The merchant that owns the contract is missing, deleted, or inactive. |
InvalidContract |
The contract's own per-bill amount is zero or less, so there is nothing to charge. |
PlanUnresolved |
The contract subscribes to a plan whose price could not be read, so the amount is unknown. |
MissingConsent |
The stored payment method has no active stored-credential consent that permits a recurring charge. |
ConsentLookupUnavailable |
The platform could not read the stored payment method's consent state. A platform fault rather than a configuration problem, recorded as a failed run item, and retried on the next run. |
Fields
| Field | Type | Description |
|---|
This model has no documented fields.