Eric Kuvykin

Reviewed October 17, 2026. This practical guide replaces an earlier general overview. The original publication date and URL are retained.

A buy-online, collect-in-store order crosses teams and systems. The useful control is a clear state transition from reserved inventory to collected goods and a recorded payment outcome.

Write the permitted order states

List accepted, ready, collected, canceled and returned as separate order events. Map each to the payment state your provider supports. Do not assume that reserving funds is the same as capturing a payment. Give store staff a visible instruction for each state and an escalation route when the payment status cannot be confirmed.

Test the handoff that is most likely to fail

Create a sample $120 order with two $60 items. Collect one item, cancel the other and inspect the system’s supported handling of partial fulfillment. The target accounting result is $60 of collected goods and a documented treatment of the remaining $60. Whether that requires a partial capture, release or refund depends on the actual integration; test it rather than prescribing a universal button sequence.

Keep one authority for money movement

If the web platform owns the payment, the store should not issue a separate terminal refund merely because it cannot see the online record. Route the request to the authorized workflow and attach the order reference. Record who approved the return and who executed the payment action. Separate inventory authorization from permission to move money.

Run a reconciliation after the customer leaves

Compare collected orders, captured amounts and refunds by order reference. Investigate duplicate capture attempts and unresolved cancellations before month-end. Visa’s current rules and policies are a primary reference for acceptance questions, but the integration’s documented capabilities determine the precise operating procedure. Keep that provider documentation alongside the test evidence.

Sources and next steps

Primary reference: Visa rules and policies. The worksheet and examples above are operational analysis, not reported customer results.

Continue through the AMS New York merchant reading path. For the broader framework, explore Eric Kuvykin’s fintech, payments, alternative financing and AI topic guides.