Shopify Flow / New ActionB2B

To Vaulted Payment Methods
"Charge Automatically When the Due Date Arrives"

A new action that lets Flow automatically charge a vaulted credit card or debit a bank account on the due date for B2B orders with payment terms.

On This Page
  1. What Was Added (Understand It in 30 Seconds)
  2. Terminology: What Are vaulted / payment terms
  3. Diagram: From the Due Date to the Charge
  4. What This Action Can and Cannot Do
  5. 5 Key Points for Developers
  6. 3 Use Cases You Can Apply to Your Business
  7. A One-Line Summary You Can Use in Pitches

1What Was Added

Added to Shopify Flow "Charge vaulted payment for B2B order" a new action.
For B2B orders with payment terms,it charges a vaulted credit card or debits a vaulted bank account at the moment the due date arrivesis performed.

Until Now: Manual Charging When the Due Date Arrived

Managing receivables for orders with payment terms (such as Net 30). Staff had to watch for the due date and run the billing and charging process manually.

From Now On: Flow Charges Automatically on the Due Date

A Flow action automatically charges or debits the vaulted card / bank account on the due date. The receivables reconciliation operation can be turned into a workflow.

The facts explicitly stated in the article are "the existence of the action," "the target being B2B orders with payment terms," "the charge target being a vaulted card or bank account," and "the execution timing being the due date" these 4 points. Details such as trigger conditions, supported plans, and supported countries are not in this announcementnot stated(see the Help Center).

2Terminology: What Are vaulted / payment terms

Term

vaulted

A payment method that the customer has registered and stored in advance. For this action, the charge / debit targets are a vaulted credit card and a vaulted bank account are the charge / debit targets.

Term

payment terms

Payment terms attached to "pay by due date"-style B2B orders. This action targets orders with these payment terms , andon the payment due datecharges them.

Term

Flow action

An "execution step" placed within a Shopify Flow workflow. Connect this action after a trigger and conditions to automate the charging process.

3How it works: from the due date to the charge

B2B order Has payment terms Vaulted payment method At time of order Payment due date payment due Trigger Flow action Charge vaulted payment for B2B order Runs automatically Charge the vaulted card credit card charge Debit from the vaulted bank account bank account debit
The specific way to configure the "trigger (payment due date)" part of this diagram (which trigger / schedule / conditions to combine) isnot specifiedin the announcement. Check the Help Center's action documentation for how to build the workflow.

4What this action can and can't do

AspectDetailsSource
Target orders B2B B2B orders with payment terms Stated in the announcement
Charge target Vaulted credit card (charge) / vaulted bank account (debit) Stated in the announcement
Execution timing When payment is due (when payment is due) is reached Stated in the announcement
Delivery form Shopify A Flow actionProvided as (integrate it into your workflow) Stated in the announcement
Supported plans / supported countries Not stated — (check Help Center)
Behavior on failure / retries Not stated — (check Help Center)

55 key points for technical teams

1. This is a "Flow action"

It's not a standalone API but a single step in a Flow workflow. It only runs when combined with a trigger and conditions. It assumes an environment where Flow is available (B2B operations).

2. There are two charge targets, and they behave differently

Vaultedcards are "charged" (charge), while vaultedbank accounts are "debited" (debit). Even with the same action, design for the fact that the processing path and settlement timing differ by payment method.

3. Execution is based on the "payment due date"

Not at the time the order is placed, but the payment terms due date is the trigger axis. How the due date is detected and connected to the action (schedule / order event) is not stated in the announcement, so the design needs validation.

RETRY?

4. Failure handling must be designed separately

The behavior on failure—such as card declines or insufficient account balance—along with retries and notifications, is not stated in the announcement.failure branches, re-charging, and operator alertsare best built as a separate branch on the Flow side.

Manual Flow

5. Position it as "automating invoice reconciliation"

At its core, this is about putting B2B's deferred-payment receivables collection operations onto Flow. The process that staff previously handled by manually managing due dates and charging is turned into a workflow, reducing reliance on individuals and human error. Verify supported plans and supported countries in the Help Center in advance.

63 use cases you can apply to your operations

USE CASE 1

Fully automate collection of "net payment (deferred payment)" for wholesale / B2B

Challenge
B2B orders with payment terms (such as net 30) are increasing, and the accounting team manages due dates and manual charging in spreadsheets, leading to omissions and delays.
Solution
Build a Flow that runs the "Charge vaulted payment for B2B order" action triggered by the payment due date, automatically charging or debiting the vaulted card / account.
Result
Eliminates reliance on individuals for receivables collection, reducing payment delays and missed invoices. Compresses the accounting team's monthly workload.
Technical note
On failure (card decline, insufficient balance), build operator alerts and re-charging in a separate branch. Confirm supported plans in the Help Center in advance.
USE CASE 2

Optimize charging by branching per payment method for cards and bank accounts

Challenge
Saved payment methods vary by partner—some are vaulted cards, others bank accounts—so collection methods are sorted manually.
Solution
Since the same action handles "charging" for cards and "debiting" for bank accounts, branch on the order's payment method while consolidating into a single collection flow.
Impact
Even with mixed payment methods, you can run a unified operation with one workflow, simplifying the design and maintenance of the collection process.
Technical notes
Card charges and bank account debits differ in settlement timing and failure reasons. It's safer to design reconciliation and dunning SLAs separately per method.
USE CASE 3

Bring billing operations in-house and hand them off "code-free"

Challenge
Collecting deferred payments requires building and maintaining a custom batch job that calls the payment API, costing engineering effort with every spec change.
Solution
Replace it with Flow's standard action and hand it off to the operations team as a no-code workflow, composed of a due-date trigger, this action, and failure branching.
Impact
Reduce the debt of custom implementation and maintenance, and let the operations side own changes to the collection logic. Engineers can focus on other development.
Technical notes
The announcement says nothing about handling via API or Webhook. For complex automation requirements, validate the due-date trigger and failure behavior in a sandbox beforehand.

7One-line summary you can use in a pitch

"For B2B orders with payment terms,Flow automatically charges vaulted cards / debits bank accounts on the payment due date.
A new action that moves the collection of deferred-payment receivables from manual, person-dependent work to a no-code workflow."