Technical update January 2026
Management API​
Product orders now include productType in responses, making it easier to identify the type of product being ordered.
We've also added a REJECTED status to help you track when orders have been rejected.
The hasRecurring parameter simplifies prefilling product orders for recurring payments.
See: Management API guide: Product orders
Recurring Payments​
This section shows new features in the Recurring Payments product and the Recurring API.
Transaction ID in charge webhooks​
Charge webhook payloads now include a transactionId field. This helps you distinguish between multiple equivalent payment operations performed on the same charge, such as multiple captures.
See: Recurring API guide: Charge webhook event payloads.
Age verification enforcement​
Starting December 9, 2025, the Recurring API enforces the age requirement by rejecting any attempt to sign a new payment agreement for users below 18 years of age.
See: Under-18 users.
Donations​
This section shows new features in the Donations product and the Donations API.
Webhook support for donation agreements​
We've added webhook support for donation agreements, allowing you to receive real-time notifications when agreements are started or stopped.
See: Donations API guide: Webhooks integration.
New agreement details endpoint​
You can now retrieve comprehensive details about a specific donation agreement using the new
GET:/donations/v1/agreements/{agreementId} endpoint.
Authentication changes for new integrations​
The Donations product now uses merchant-level API clients for authentication. You'll receive a client ID and client secret in the portal, and use Specialized Authentication to get your bearer token.
If you already integrated based on a Recurring Donations API client, it will still work, but we recommend moving to the merchant-level client once you have been approved for the Donations product.
See: Donations API guide: Integration steps.
Login​
This section shows new features in the Login product and the Login API.
Custom consent collection flows​
The new customFlow scope enables merchants to fully customize their consent collection experience using the flow builder in the business portal.
This is the recommended approach for new integrations requiring custom consent flows.
See: Login API: Collecting consents.
Partner portal support​
Partners can now manage Login product settings for their merchants directly from the partner portal.