The paymentMethod/updated webhook now returns two additional keys - source and entity - so you can identify where a payment method action originated and who performed it.

• source indicates the platform or interface from which the action was taken. Possible values: Admin Portal, Customer Portal, API, Shopify.
• entity provides additional context about the initiator, and its value depends on the source:
  • Admin portal - the email address of the user who performed the action
  • Customer portal - null if taken directly by the customer, or API if performed via the Storefront API
  • API - the name of the API token used to make the request
  • Shopify - null

Things to remember

These keys are included automatically in all paymentMethod/updated webhook payloads - no changes needed on your end to start receiving them.

We’ve introduced new API capabilities that allow brands to add or remove a backup payment method for a subscription. This helps ensure better payment recovery by enabling a secondary payment method that can be used if the primary payment fails.

What's new?

New API endpoints:

• Add backup payment method - Add a backup payment method to an existing subscription.
• Remove backup payment method - Remove an already mapped backup payment method from a subscription.

Headless portal support:

• Brands using a headless customer portal can also leverage an Add backup payment URL, similar to the existing Add/Update payment method flow.
• This URL can be shared with brands upon request.

The subscription/updated webhook now includes a previous object in the payload, giving you a snapshot of the subscription's state before the change was applied.

What's New?

You can now compare the previous and current state of a subscription directly from the webhook payload - no database required. The previous object is available across the following changes:

• Line actions - swap, quantity update, product added or removed (for both subscription and one-time lines)
• Discount actions - discount added or removed
• Policy updates - changes to billing policy or delivery policy on a subscription contract

Why this matters

This is especially useful if you're running automations or workflows based on subscription changes but don't maintain your own database. With the previous object, you can now detect exactly what changed and trigger the right action downstream - without needing to store or compare historical states yourself.

You can now update a subscription's line item directly via the Admin API using the new Edit line endpoint.

What's New?

A new endpoint is now available under Line Actions in the Admin API. It allows you to modify quantity of an existing line item on a subscription.

Currently supported updates:

• quantity — Update the quantity of a line item on the subscription.

Things to remember:

1. Support for updating price will be available soon.
2. Changes made via this endpoint apply to all future orders on the subscription.

You can now remove a line item from a subscription's upcoming order without affecting future orders using the new Remove line once endpoint.

What's New?

A new remove line once endpoint is now available under subscription line actions in the Admin API. It removes a specific line item for the next order only -the line item subscription resumes as normal from the following order onwards.

Things to remember:

1. This only affects the immediate upcoming order. The line item will be restored automatically for subsequent orders.
2. Use the existing Remove line endpoint if you want to permanently remove a line from the subscription.

We’ve introduced a new endpoint that allows brands and integrations to retrieve the subscription ID associated with a specific Shopify order ID. This simplifies identifying which subscription generated a particular order and enables smoother workflows for support, reporting, and external integrations.

What's New?

The following endpoint is now available in the developer APIs:

• Read subscription by Shopify order ID - Fetch the subscription ID linked to a specific Shopify order ID, making it easier to identify the originating subscription for any order.

Compatibility / Impact

No breaking changes. This is a new endpoint and does not affect any existing API behavior or integrations.

Three new fields have been added to the subscription object returned by key Admin API endpoints, giving you richer subscription data without additional API calls.

What's new?

The following keys are now available in the response payload of the Read all subscriptions, Read subscriptions for customer , and Read subscription details endpoints:

• nextBillingDate - The date on which the next billing attempt is scheduled for the subscription.
• orderInterval - The frequency interval at which orders are placed for the subscription.
• completedOrdersCount - The total number of orders successfully completed under the subscription.

Compatibility / Impact

No breaking changes. These are additive fields; existing requests and integrations will continue to work as before.

You can now migrate customer payment methods from external payment processors directly into Shopify using the new Admin API endpoint - making it easier to bring existing payment data into Loop and create subscriptions without manual intervention.

What's New?

1. New Migrate customer payment method endpoint: A new POST endpoint is now available under Payment Methods in the Admin API. It allows you to migrate a customer's payment method from a supported third-party payment processor into Shopify.
   • Supported processors: Stripe, Authorize.Net, Braintree, PayPal
   • On successful migration, the response payload will include a paymentMethodShopifyId - the Shopify payment method reference you can use downstream to create or manage subscriptions.
2. [Improvement] paymentMethodShopifyId now accepted in Create subscription endpoint: When creating a subscription via the Admin API, you can now pass paymentMethodShopifyId as an alternative to Loop's internal paymentMethodId. This is particularly useful when the payment method has been migrated from an external processor and a Loop internal ID is not yet available.

Things to remember:

1. The paymentMethodShopifyId is returned in the response of the migrate payment method endpoint and can be passed directly into the create subscription call.
2. Ensure the payment token from the third-party processor is valid and active before initiating migration.

You can now retrieve cancellation flow logs directly through the Admin API using the new cancellation flow logs endpoint.

What's New?

A new Fetch cancellation flow logs endpoint is now available under the Cancellation Flows section of the Admin API. This allows you to pull logs of customer interactions across your cancellation flows, giving you a clearer picture of how subscribers are engaging with benefits page, cancellation reasons and offers.

Use this endpoint to:

• Audit cancellation flow activity - see what reasons customers are selecting and what offers are being presented.
• Measure retention performance - track which offers are being accepted or declined across flows.
• Support reporting workflows - export flow log data into your internal dashboards or analytics tools.

Things to remember:

• Cancellation flows must be configured in your Loop app before logs are generated.

The subscription/created webhook now includes a new prepaidIntervalCount boolean in the billingPolicy object, improving visibility into prepaid subscription billing cycles at the time of creation.

What's New?

A new prepaidIntervalCount boolean is now available in the billingPolicy object of the subscription created webhook. When used together with the prepaid billing interval count and delivery interval count, it allows brands to accurately calculate the number of orders in a prepaid cycle. This enhancement is especially useful for brands relying on third-party fulfillment services, as it enables better inventory forecasting and operational planning based on newly created subscriptions.