Skip to main content
​
June 12, 2026
WorkflowsSubscriptionsDashboard
Added plan switching in post-payment workflows, Split node improvements, and dashboard customization.

​
Plan switching in workflows

Payment Status Changed workflows can now switch a subscription to a different plan as a recovery action after failed or declined payments.
  • New condition: Current plan is — evaluates the current subscription plan at execution time, with equal, not equal, one of, and not one of operators.
  • New action node: Change Subscription — permanently switches the subscription to the selected plan. The subscription keeps its current currency; if the target plan cannot be applied for that currency, no change is made.
  • The current dunning schedule is not affected — future billing after dunning uses the new plan.
Both are available only in workflows started by the Payment Status Changed trigger.

​
Split node improvements

  • Route-level metadata can now be configured directly on the Split node — no extra Set Metadata nodes needed for route tagging.
  • New Preserve route assignment (CIT only) option: repeated CIT attempts in the same checkout session reuse the previously assigned route instead of being redistributed.

​
Dashboard settings

Admins can now customize the dashboard for their organization:
  • Hide or reorder dashboard tabs.
  • Hide or reorder chart cards within each tab.
  • Settings are organization-wide and apply to all members.
​
June 10, 2026
APISearchSubscriptionsDevelopers
Released API version 2.0.0. This version adds a search query language on the list endpoints, returns a consistent search envelope, and consolidates the subscription cancellation endpoints.

​
Opt in with the X-API-Version header

Set the X-API-Version: 2.0.0 header on every request to use this version. Without it, endpoints keep their 1.0.0 behavior and response shape, so existing integrations are unaffected until you opt in.

​
Search on list endpoints

GET /payments, GET /customers, GET /subscriptions, and GET /plans now accept a single query parameter written in the PayNext search query language, plus page and limit for pagination. The legacy per-field filter parameters — payment_status, amount_from, amount_to, created_from, metadata_in, subscription_status, and the rest — are removed in favor of the query language.For query syntax, fields, and examples, see Search.

​
Consistent search envelope

The list endpoints now return a standard envelope instead of a bare array:
  • object — the result type
  • data — the matching records
  • total_count — total number of matches
  • has_more and next_page — pagination cursors
  • url — the request path

​
Subscriptions — list endpoint moved

GET /subscriptions/search is replaced by GET /subscriptions, matching the search pattern used by the other list endpoints.

​
Subscriptions — one cancellation endpoint

POST /subscriptions/schedule-cancel/{id} is removed. POST /subscriptions/cancel/{id} now takes a required type field that routes between the two strategies:
  • cancel_immediately — transitions the subscription to cancelled right away.
  • schedule_cancellation — marks it for cancellation at the next billing date. This is idempotent if a scheduled cancellation already exists.
​
June 08, 2026
FiltersWorkflowsDevelopersPermissions
Added card-based routing conditions, role-based API key access controls, and API key usage visibility.

​
Card funding type and card segment

Two new fields are now available for filtering payments and configuring workflow conditions: Card funding type and Card segment. Both apply to card, Apple Pay, and Google Pay payment methods.Card funding type values: Debit, Credit, Prepaid, Deferred Debit, Charge Card.Card segment values: Consumer, Business, Commercial, Government, Payouts, General Purpose.
  • Payments page: both fields are available as filters with one of, not one of, is not null, and is null operators.
  • Workflow Builder: both fields are available as conditions with equal, not equal, one of, and not one of operators.

​
API Keys — role-based access

Access to API keys is now controlled by role:
  • Member role: API key values are hidden and key creation is disabled. Integration credential fields are read-only.
  • The full API key value is shown only once — immediately after it is created. A warning at creation prompts you to copy and store it securely; it cannot be retrieved afterward.

​
API Keys — usage visibility

The API Keys table now shows two additional columns:
  • Last used — date the key was last used to authenticate a request. Shows — if the key has never been used.
  • Created by — name and email of the user who created the key. Keys created before this update have no recorded author and will always show —.
​
June 04, 2026
Fraud PreventionMastercardAPIFilters
Mastercard Consumer Clarity is now live—Mastercard’s equivalent of Visa Order Insight, surfacing the transaction receipt to cardholders to deflect friendly fraud before disputes are filed.

​
Mastercard Consumer Clarity

Mastercard Consumer Clarity enriches the transaction receipt a cardholder sees—inside their mobile banking app or when they call their bank about a charge. The cardholder recognizes the charge, and friendly-fraud disputes on Mastercard are defused before they’re filed. Once enrolled (by statement descriptor), the integration is fully managed—no code changes required. See Mastercard Consumer Clarity.
  • New fraud_prevention.mastercard_consumer_clarity payload. Every lookup is written to the payment as a sub-object with type (the lookup channel—DIGITAL, CALL_CENTRE, MASTERCOM, or TRANSACTION_DATA), insight_id, and updated_at, and delivered on the payment.updated webhook.
  • Payments filter. Added a Fraud Prevention – Mastercard Consumer Clarity Channel filter on the Payments page. Supports one of, not one of, null, and not null. Values are sourced live from payment data.
  • Payment timeline. Consumer Clarity events now appear as Mastercard Consumer Clarity (<TYPE>), alongside existing Visa Order Insight and RDR rows.
  • Subscriptions are unaffected. A Consumer Clarity lookup is informational—it does not cancel or change the subscription, unlike a Visa Order Insight call-centre lookup.
​
June 03, 2026
DashboardSubscriptionsFilters
Added a custom analytics tab, new dashboard filters, and a plan change mode for subscriptions.

​
Dashboard — Custom tab

A new Custom tab is now available on the Dashboard. It provides a flexible dimension table where you can break down payment metrics by up to three dimensions simultaneously — processor, card network, issuer country, BIN, currency, and more. Columns are sortable and include key counts, amounts, acceptance rate, decline rate, and refund rate.

​
Dashboard — BIN Analysis

Added Acceptance Rate by Merchant Account and Card Network heatmap to the BIN Analysis tab. Shows acceptance rate per merchant account broken down by Visa and Mastercard, with color indicators for performance thresholds.

​
Dashboard — Filters

  • Added Dunning Attempt filter on Payments, 3DS, and Declines tabs.
  • Added Amount (USD range) filter with predefined brackets.
  • Added Statement Descriptor filter.
  • Added Currency Code filter.
  • Decline Advice Code, Decline Code, and Decline Message filters are now available on Payments, 3DS, and Declines tabs.

​
Subscriptions

  • Added change_mode field to the scheduled plan change flow on the PATCH subscription endpoint: next_billing_date (default) applies the change at the next billing date, immediate applies it now with no charge and recalculates the next billing date.
  • Creating a client session with proration_billing_mode: prorated_immediately when the prorated amount is below $0.50 now returns a 400 error instead of attempting a payment that would fail at the processor.
​
June 01, 2026
WorkflowsCascadingSubscriptionsAPI
Added declined payment cascading, new workflow routing conditions, PII erasure support, and subscription metadata updates.

​
Declined payment cascading

Workflows can now cascade to another processor after an unsuccessful authorization within the same payment flow. If conditions match after a decline or failure, the workflow executes another authorization attempt on a different processor without creating a new payment.Existing payment outcome conditions (decline code, advice code, decline message, failure reason, past due attempt number) are now also available for cascading routing.Available for MIT routes only:
  • Last Used Processor — processor used in the last successful authorization for this user
  • Last Used Merchant ID — Merchant ID used in the last successful authorization for this user
Current Processor and Merchant ID have been removed as payment workflow conditions and replaced by the two fields above.Other changes:
  • Use merchant from CIT toggle is renamed to Use last successful processor.
  • Payment timeline now shows all authorization attempts in sequence when cascading occurs in the same payment flow.
  • All authorization nodes within a cascading flow must use the same 3DS mode — inconsistent configurations block Save / Publish.

​
Customer API

  • PATCH customer endpoint now supports updating email, full_name, phone, address, and metadata.fingerprint.

​
Subscriptions API

  • Update Subscription endpoint now accepts a metadata field. Changes emit a single subscription.updated event.
​
May 15, 2026
WorkflowsCheckoutDashboardFilters
Improved organization navigation, workflow usability, Fraud Prevention filtering, and added refund visibility to the Dashboard.

​
Workflows

  • Condition details are now visible in View mode on hover — no need to enter Edit mode to inspect conditions.
  • Deleting the last active workflow for a payment method now shows a confirmation modal and immediately disables that method in Checkout.

​
Dashboard

  • Added Unsettled Refunds stacked bar chart on the Payments tab, showing refund breakdown by status (Settling / Settled).

​
Filters

  • Fraud Prevention filter on the Payments page now works as a simple presence check — use Is null / Is not null to filter payments that have or don’t have fraud prevention data attached.
​
May 01, 2026
WorkflowsSubscriptionsNotificationsFilters
Added post-payment workflow automation, in-app notifications foundation, and several dashboard usability improvements.

​
Workflows and subscriptions

  • Added the new Payment Status Changed workflow trigger.
  • Workflows can now run on Payment Failed or Payment Declined outcomes.
  • Added payment outcome conditions:
    • payment decline code
    • payment advice code
    • payment decline message
    • payment failure reason
    • past due attempt number
  • Added subscription cancellation actions:
    • cancel immediately
    • schedule cancellation

​
Notifications

  • Added organization-scoped in-app notification delivery through the notifications feed.
  • Added the foundation for future operational alerts, product updates, and Slack-based notifications.

​
Dashboard improvements

  • Payments page now supports a Failure Reason filter.
  • Newly selected filters now appear at the top of the applied filters list.