Skip to main content
PATCH
Update Subscription
Subscription TransitionThe fields billing_cycles and availability.finish_at have an impact on each other. If both are completed during the subscription creation, it will transition to the COMPLETED state upon reaching the nearest event defined in these fields, whether it is the billing cycle or the corresponding finish_at.
Retroactive Credential UpdateIf you have existing subscriptions that are failing rebills because of missing credential usage (e.g. from an initial CIT payment), you can use this PATCH endpoint to add the store_credentials object retroactively to fix the issue.

Authorizations

public-api-key
string
header
default:<Your public-api-key>
required
private-secret-key
string
header
default:<Your private-secret-key>
required

Path Parameters

id
string
required

The unique identifier of the subscription.

Body

application/json
name
string

The subscription plan name (MAX 255; MIN 3).

description
string

The subscription plan description (MAX 255; MIN 3).

account_id
string

The unique identifier of the account that will have the subscription plan available to use (MAX 64 ; MIN 36).

merchant_reference
string

Identification of the subscription plan (MAX 255; MIN 3).

soft_descriptor
string

Statement descriptor shown on the cardholder's bank statement. Updating it changes the descriptor applied to subsequent rebills generated by the subscription engine. Length and formatting limits vary by provider (for example, Unlimit truncates to 22 characters and Airwallex to 30). Worldpay does not read this field; it builds the statement narrative from payment_description instead.

Maximum string length: 255
country
string

The subscription's country.

amount
object

Specifies the amount object, with the value of each subscription payment and the used currency.

frequency
object

Specifies the frequency object. Defines the billing frequency for the subscription. Including type and value.

billing_cycles
object

Specifies the billing_cycles object. Defines the number of charges associated to the subscription.

customer_payer
object

Specifies the customer_payer object to identify the customer.

payment_method
object

Specifies the payment_method object. Currently, only card as available as payment methods. You can use the card token, the vaulted_token or the card information using through the card object.

availability
object

Specifies the availability object. Defines a date interval based on starting and ending dates when the subscription is available to use.

retries
object

Specified the 'retries' object. If we need to retry declined transactions in Yuno and the amount if necessary. If modified, the retries will apply to the next payment intent.

metadata
object

Set of key-value pairs that you can attach to an object. This can be useful for storing additional information about the object in a structured format. Individual keys can be unset by posting an empty value to them. All keys can be unset by posting an empty value to metadata.

Response

200

id
string
Example:

"0c7fed3e-ee0d-4d34-9547-778be4ec0798"

name
string
Example:

"Test Subscription"

account_id
string
Example:

"493e9374-510a-4201-9e09-de669d75f256"

country
string
Example:

"US"

description
string
Example:

"Subscription Test"

merchant_reference
string
Example:

"subscription-ref-merchant-AA01"

soft_descriptor
string
Example:

"ACME SUBSCRIPTION"

status
string
Example:

"ACTIVE"

amount
object
frequency
object
billing_cycles
object
customer_payer
object
payment_method
object
availability
object
metadata
any
created_at
string
Example:

"2024-09-30T12:04:23.265372Z"

updated_at
string
Example:

"2024-09-30T12:04:23.265372Z"