Platform
🟢 Braintree Payment Integration
We are excited to announce the integration of Braintree as a payment processor on our platform! This update offers more flexibility and security for your payment processing needs while providing comprehensive support for 3D Secure (3DS) transactions. With this integration, platform admins can easily enable or disable Braintree, and customers can smoothly complete transactions with enhanced security features.
Key Highlights:
Full Braintree integration for secure payment processing.
Complete 3DS support for new subscriptions, renewals, payment method additions, and invoice payments.
Accurate webhook payloads reflecting Braintree invoice links.
Aligned with platform billing settings, including automatic payment method updates and card decline handling.
🟢 Enhanced Reporting and New Insights:
We’ve made some improvements to our reporting features to provide you with more actionable insights and a more intuitive data experience:
Table View Changes: The reporting table now features a more intuitive column order for better data clarity:
Time - Series - Value
Export Changes: To improve readability, the format of the "created" field in both Subscriptions and Payments exports has been modified from a timestamp to a date-only format (DD/MM/YYYY). Additionally, the column position of the "created" field has been adjusted.
Adjustments to existing reports:
Gross Volume has been renamed to Payments Volume:
New Phases has been renamed to Renewed Subscriptions:
New Reports Introduced:
Failed Payments: Stay informed of payment issues by tracking the number of new failed payments within a specific timeframe.
🟢 A new optional field, "Refund Reference," has been added to the refund creation process. This field allows to manually record a reference or a specific payment ID associated (for example, associated with a customer balance transaction). This will enable easier tracking of the source of funds during cash reconciliation.
Optional "Refund Reference" field added to refund creation (Supports text input).
Surfaced in refunds section, refunds exports and API responses.
Backwards compatibility ensured.
🟢 Direct Modification of Collaborator Access and Roles:
This update streamlines collaborator management by allowing Site Owners and Administrators to directly modify an existing collaborator's site access and role without the need for removal and re-addition. With the addition of editable fields for Role and Sites in the Edit Collaborator section, administrators can efficiently manage permissions, reducing the risk of errors. Additionally, all collaborator update actions are now recorded in the Platform activity logs, ensuring enhanced traceability and security for all changes made.
🟢 Introduced country availability settings for individual SKUs:
This update introduces the ability for e-commerce businesses to set country availability for individual SKUs, ensuring that each SKU is available only in the appropriate regions. The SKU creation and editing pages now include a field for setting country availability. Additionally, added a new optional countries parameter in the Create SKU and Update SKU Core API endpoints, allowing businesses to define targeted country codes for the SKU. Webhooks have also been updated to include the countries attribute in ecommerce_sku.created and ecommerce_sku.updated events, and will trigger accordingly when country availability is modified.
🟢 Improved List Builder with New "Membership Role" Filter
A new "Membership Role" section has been added to the list builder, providing greater control over who receives membership deliverables. This filter lets you include or exclude Membership Owners, Members, or both when creating, reusing, or viewing subscription lists. This enhancement ensures that deliverables are accurately sent to the correct recipients, minimizing delays and confusion regarding the roles of membership owners and members.
APIs
🟢 Added a new optional attribute default_source_id to the Update Customer API to allow administrators to manage customer default payment methods directly through the Core API. The new attribute accepts the ID of an existing customer payment method. This also mirrors platform behavior related to "Automatic update of default payment method" setting (i.e. If enabled for the customer, updating the default source ID will also update all their subscriptions to use the new payment method).
🟢 Added a new optional countries attribute to the Create SKU and Update SKU Core API endpoints, allowing businesses to define targeted country codes for the SKU. This attribute accepts an array of ISO 3166-1 alpha-2 country codes (e.g., ["US", "CA", "GB"]), specifying the regions where the SKU should be available.
Comments