A selected Shopify card provider is ready for wider use only when the team can trace a checkout attempt through authorization or capture, refund, and the appropriate financial records. This runbook produces that acceptance evidence for a store owner, support lead, and finance lead. It assumes provider eligibility and selection have already been resolved.
Run the checks against the chosen Shopify integration and intended capture setting. Mark each result as passed, failed, not reproduced, or not supported, with evidence and an owner. Official documentation was checked on October 4, 2026. The checks below are a proposed acceptance procedure, not results from a WESWOO store test.
Prepare a test environment and a case record
Prepare an isolated store and follow Shopify's test-mode requirements: complete setup, use a paid plan, pause automatic fulfillment, and avoid shipping-label purchases. Shopify advises against enabling this mode on a production store.
For Shopify Payments, open Settings > Payments > Shopify Payments > Manage, enable test mode, and save. For a third-party integration, use its own Shopify Checkout test instructions and credentials. Shopify's Test payment gateway can check a generic checkout workflow, but its success doesn't establish that a separate provider's integration works.
Before each attempt, record the case ID, integration name, test or live environment, date and time zone, market, checkout currency, amount, capture setting, and expected outcome. Afterward, add the order or abandoned-checkout reference, payment event, observed status, and evidence location. Use separate cases for different currencies and payment routes so that failures remain reproducible.
Prove successful capture and deliberate failure
With Shopify Payments test mode enabled, enter a cardholder name with at least two words, a future expiry date, and any three-digit security code for these Visa test cards. American Express test cards require four digits instead. The test purchase must be greater than the equivalent of US$1 in the checkout currency. These are simulation-only credentials, following Shopify's test-input requirements.
Initial Shopify Payments test cases
| Case and input | Evidence needed to pass | Failure handling |
|---|---|---|
Successful Visa payment: 4242424242424242. | A single test order and the expected payment event for the configured capture method. | Open the order's payment details; investigate a mismatch before treating checkout confirmation as acceptance. |
Generic decline: 4000000000000002. | An unsuccessful checkout attempt with the expected failure recorded; no successful capture for that attempt. | Inspect the failed payment event rather than repeatedly retrying. |
Insufficient funds: 4000000000009995. | A separate recorded failure, distinguishable from the successful case. | Check that support can find the attempt and its returned message. |
These inputs come from Shopify's test-card guide. A test-mode banner identifies simulated orders; simulated transactions don't establish a real payout.
If manual capture is intended, the successful case should first show Authorized. Open Orders > the order > Capture payment, review the amount, and complete capture within the provider's authorization period. Then check the successful capture in the timeline and the change to Paid. These are the steps in Shopify's capture guide. With automatic capture, verify the actual capture event without introducing an unnecessary manual step.
Also run one controlled retry case in the test environment, such as returning after an interrupted attempt and submitting again. Match all resulting attempts and transactions to the case. Pass only when the final order and charge count are understood; an unexplained second order or capture is a blocker. Don't assume that refreshing, a timeout, or a confirmation page determines whether money moved.
For failed attempts, go to Orders > Abandoned checkouts and open the checkout's timeline; recent attempts may need time to appear. For an existing order, inspect its own timeline. Shopify documents these two evidence paths in checkout payment troubleshooting.
Record the limits of the 3DS check
In Shopify Payments, 3DS is used when required by the issuing bank; a successful payment without a challenge doesn't prove a challenge flow was exercised. Check the documented 3DS flow. The Shopify Payments test-card guide doesn't supply a dedicated challenge card. Don't import another platform's sandbox numbers and label the Shopify integration verified.
- If the selected integration has documented Shopify-connected 3DS test scenarios, run successful completion and an abandoned or failed challenge using those instructions. Record the instructions and scenario identifiers alongside the result.
- Check the resulting payment event and order state. Shopify's 3DS failure guidance explains where failed authentication appears in the abandoned checkout. Record the actual event instead of interpreting the customer's browser screen alone.
- If no supported challenge simulation is available, mark the challenge outcome not reproduced. Ask the provider which evidence it supports, assign an owner to review any challenge encountered during the controlled live rollout, and retain that limitation in release approval.
Agree a support response before launch: locate the attempt, distinguish unfinished verification from a confirmed payment, and guide a deliberate retry or an available alternative after checking its state. Never remove authentication controls to make an acceptance case pass. A rollout approval must state who handles unresolved challenge or redirect incidents.
Run a partial refund, then refund the remainder
Use a captured test order with a clearly recorded amount. In Orders > the order > Refund, choose the quantity or refund amount, check shipping and restocking choices, and select the original payment method. Review the summary and notification option before submitting. Verify the partial refund event and Partially refunded status; then refund the remaining available amount and check the final record. Follow Shopify's refund procedure.
For each refund, retain the amount, currency, original transaction reference, refund reference where available, and resulting event. The amounts returned must match the intended partial-plus-remainder total. A submitted refund can't be canceled, so check the summary before confirming.
A pending or failed refund isn't a successful refund case. Open the timeline, note status and error, and review the provider's refundable window and the payment method. For Shopify Payments, check the balance and notifications; a negative-balance limit can delay refunds. For a third-party provider, inspect its dashboard and returned failure reason. Follow refund troubleshooting and assign finance or support to resolve the exception before issuing another refund.
Accept live money movement separately
Test mode proves simulated payment and order handling. Its transactions don't appear in payouts or financial reports. It also excludes some methods, so log any method that needs a different supported test route. Before live acceptance, restore the intended provider configuration, deactivate test mode, and verify that the correct account is active.
Arrange an owner-approved, small real purchase on the intended live route using legitimate payment details. Record its costs and keep fulfillment controlled. To verify a bank credit, trace capture through the payout and bank entry before issuing the planned refund, within the provider's refund window. Then trace the refund's financial effect separately. If an earlier refund offsets the sale before payout, that case hasn't proved a bank credit; keep the deposit check outstanding until an approved captured sale produces one. Keep the rollout limited while that evidence remains outstanding.
- For Shopify Payments, open Finance > Payouts. In the new view, click the payout date, choose the specific payout, then click the Export icon and Export payout transactions. This view is in early access and available only to some merchants. In the original view, click the date and, if needed, the specific payout for that day, then Export > Export payout transactions. Match the displayed interface to Shopify's payout-detail guide.
- Match order references and transaction types to the captured payment and refund. Compare amount, fee, net, currency, and payout reference. Include adjustments and reserves that explain the deposit instead of subtracting only the refund from the order total.
- Match the payout's transfer reference, when available, and amount to the bank entry. Shopify's Deposited status means the transfer was sent to the bank; it doesn't establish that the bank has credited the account. Resolve a failed payout through the admin's next-step instructions and bank or provider support.
- For a third-party gateway, obtain its settlement export and bank reference. Check Shopify's platform fee separately in Settings > Billing > the relevant past bill. The third-party fee breakdown is a separate record from the provider's payout.
Use the Shopify Payments activity report for period review, not as a replacement for tracing a specific deposit. It excludes Shopify billing fees and third-party processors. When records differ, check currency, date range, time zone, payout timing, and the report's data delay before declaring money missing.
Make exceptions part of the release decision
The owner should sign off the evidence for success, failure, capture, refund, and financial reconciliation, plus explicit limitations for 3DS or unsupported methods. Support owns unmatched checkout attempts, finance owns refunds and payout differences, and the provider or integration team owns unexplained payment-state mismatches.
Pause broader rollout for a captured payment without a matching order, unexplained duplicate capture, untraceable refund, or deposit mismatch. Gather the case ID, timestamp, method, currency, references, exact error, and steps already taken; then escalate through the responsible provider. Confirm the actual transaction state before asking for another payment or manually marking an order paid. Keep payment evidence limited to the necessary references and masked details.
Prepare dispute handling as an operational drill using the provider's documented process: confirm who receives notices, who owns the response deadline, and where order, delivery, and refund evidence is kept. Shopify distinguishes chargebacks from inquiries, with different immediate financial effects. A drill proves the team's process; it doesn't establish a future dispute outcome.
FAQ
Does Paid status alone prove that the correct card payment settled?
No. Shopify's status definitions include orders manually marked as paid. Check the payment transaction and then the provider's payout and bank evidence.
What if a customer or tester reports a charge with no order?
Check orders, abandoned-checkout events, and the provider's transaction status before requesting payment again. Distinguish an authorization hold from a completed charge and escalate an unmatched completed payment.