A wholesale order paid by link
Before the manager creates a payment link in Stripe by hand, then checks later whether it was paid and updates Shopify.
After the link comes from the order itself, and the paid order moves to fulfilment on its own.
Shopify orders agreed outside the checkout get a Stripe payment link, a confirmed Stripe payment moves the order on, and Stripe subscriptions turn into Shopify orders for each delivery
Most Shopify orders are paid at checkout, and this pair does not replace that. It is for the orders that do not fit: a wholesale buyer who agrees the order with a manager, a client abroad who pays by link, a monthly box sold as a Stripe subscription. Then the money is in Stripe, the order is in Shopify, and someone connects them by hand. The Shopify ↔ Stripe pair sends a Stripe payment link for the Shopify order, moves the order on when Stripe confirms the payment, and creates a Shopify order for each paid subscription period so the warehouse sees what to ship. Below: what exactly moves, which scenarios we cover and which capabilities of both systems we rely on.
Before the manager creates a payment link in Stripe by hand, then checks later whether it was paid and updates Shopify.
After the link comes from the order itself, and the paid order moves to fulfilment on its own.
Before subscriptions are paid in Stripe, and the warehouse works from a table someone updates by hand.
After every paid period appears as a Shopify order, and a failed payment stops the box before it ships.
Before a refund is made in Stripe, and the Shopify order still looks paid at month end.
After a line about the refund is added to the order note without erasing what the team wrote there before, and the two systems tell the same story.
For those who want to check: each point links to the official documentation page it comes from.
An order can be created through the API outside the regular checkout — Shopify itself suggests this for orders imported from an external system or for wholesale customers.
Source: shopify.dev ↗ checked 2026-09-29An order can be marked as paid through the API: Shopify records a payment for the outstanding amount — this is meant for payments taken outside its checkout.
Source: shopify.dev ↗ checked 2026-09-29When an order is updated, its note and tags are replaced entirely, so a new tag or line must be sent together with the existing ones.
Source: shopify.dev ↗ checked 2026-09-29Payment Links, Stripe's no-code hosted payment page, support 40+ payment methods, send automatic receipts and allow no-code refunds directly from the dashboard.
Source: docs.stripe.com ↗ checked 2026-09-25Webhook authenticity is confirmed by checking the Stripe-Signature header against a signing secret issued when the endpoint is set up; the receiving server should respond quickly with a 2xx status instead of running long business logic inside the handler, and Stripe's official libraries allow a default 5-minute tolerance between the signature timestamp and server time.
Source: docs.stripe.com ↗ checked 2026-09-25When a subscription is created, Stripe automatically generates invoices, attempts to collect payment and manages the subscription's status through its whole lifecycle; with automatic charging, Stripe creates an invoice with an open status and gives the customer 23 hours to pay, during which the subscription stays incomplete.
Source: docs.stripe.com ↗ checked 2026-09-25The limits come from both systems. This pair does not change how your Shopify checkout takes payments; it covers orders paid outside it and Stripe subscriptions. Stripe expects the receiving side to answer its notifications quickly, so the pair records each one first and does the order work afterwards. A new Stripe subscription waits up to 23 hours for its first payment, and no Shopify order is created until that payment succeeds. Marking an order paid records the amount still due, and the order note is replaced as a whole on update, which is why the pair always reads the old note first. Access to the store is granted by its owner, and refunds are always made by a person.
Three steps from a first message to work on your project.
Describe the task in the form — in text or by voice. Budget and timing are optional.
A developer studies the brief, asks about anything unclear and sends an estimate.
Once scope and price are agreed, the work begins.
or write to info@coreviaflow.space
Describe the task in text or a voice message. We look at your setup and reply with a plan.
Four services people come to us for most often. Each page explains what we do, how the work goes and where to start.
Choose the system, set up the pipeline, migrate data, train the team.
Learn more →Accounting, telephony, website, payments and messengers feed the CRM on their own.
Learn more →Orders, requests and answers around the clock, straight into your CRM.
Learn more →Flows between CRM, email, spreadsheets, payments and AI, on your own server.
Learn more →Orders from your Shopify store flow into your CRM, delivery and mailing on their own
See scenarios →One checkout for 125+ local payment methods, plus automatic tax and subscription billing
See scenarios →PayPal payments for orders agreed outside the checkout find their Shopify order, mark it paid and move it to fulfilment, and refunds go back the same way
See scenarios →Every Stripe payment lands in QuickBooks Online as a payment against the right invoice, with processing charges and refunds accounted for
See scenarios →Every Stripe payment closes the right Xero invoice, processing charges and refunds are booked, and payouts match the bank feed
See scenarios →A Shopify order gets a LiqPay payment link or an invoice to email, and a confirmed LiqPay payment finds its order and moves it on, without anyone checking two screens
See scenarios →Implementation · Development · Integrations →
Shopify ↔ Stripe — the system names are trademarks of their owners. CoreviaFlow is not affiliated with them unless stated otherwise.