Build the payment flow around the order you can actually deliver
A payment gateway approves a transaction; it does not confirm that a supplier has stock, that an address is serviceable, or that the parcel can enter its destination market. A China dropshipping store needs those decisions connected before it releases an order. Otherwise, a successful payment becomes a refund, a customer complaint, or a dispute while the product is still waiting at origin.
Start with the legal business that will receive the money. Check a provider's supported countries, business categories, verification requirements, settlement currencies, and prohibited-business rules against that entity. Do not use someone else's account or describe the business as domestic fulfillment if customers receive cross-border parcels. Approval for one entity or website does not establish approval for another.
Separate customer currency from supplier currency
There are three different amounts to reconcile: the price presented to the customer, the amount settled to the merchant, and the amount paid to the supplier. Currency conversion can occur between each pair. A refund may happen at a different exchange rate from the original payment, while a supplier may deduct a transfer charge from the money received.
Record the original transaction currency and the settlement currency alongside the order. Keep supplier invoices in their original currency and show conversion costs separately in the margin report. This makes it possible to distinguish a poor exchange rate from an expensive shipping lane or a product price increase.
Before offering a new currency, run a small, legitimate test purchase and refund using the provider's supported testing or merchant procedures. Confirm how the customer sees the price, which currency reaches the settlement account, and how the accounting system represents the refund. A currency selector in a theme does not prove that checkout and settlement work as expected.
Decide when an order becomes releasable
An operational release should require a usable address, a supported product and destination, sufficient available stock, and the payment state your business has chosen to accept. An authorization is different from a captured payment. Review the gateway's authorization window before designing a workflow that waits several days for supplier confirmation.
Risk review needs its own state. An order held for review must not be passed to the warehouse simply because an order-created notification arrived first. Staff should be able to see who released a hold and why. If an address changes after payment, preserve both the original order details and the approved change rather than overwriting the history.
Split orders need particular care. If only one item is available, obtain the customer's agreement to the proposed handling and record any partial refund. The fulfillment record, refund record, and customer message should describe the same outcome.
Prepare evidence while the order is moving
Stripe's dispute guidance distinguishes delivery disputes from claims about product quality. Evidence should answer the reason actually raised. A dispatch scan cannot, by itself, demonstrate delivery, and proof of delivery cannot establish that an item matched its advertised specifications. Stripe's evidence examples illustrate this distinction.
Maintain an order-level record containing the purchased product and variant, the product page as offered, agreed delivery information, customer correspondence, tracking events, and any refund. For a quality complaint, add the relevant inspection record and the proposed remedy. Keep evidence readable and relevant rather than submitting an unstructured warehouse export.
Customer communication belongs in this record. If a parcel is delayed, explain the latest verified event and the available resolution. Do not ask a customer to withdraw a dispute as a condition of receiving a refund that the business already owes.
Reconcile cash and exceptions together
Review orders, settlements, supplier payments, and refunds as connected ledgers. An order can look profitable in the storefront while its settlement is reduced by conversion costs, a replacement shipment, and a dispute fee. Set aside operating cash for those exceptions instead of treating every settled payment as money available for advertising.
Useful review measures include the share of paid orders held before release, refunds before dispatch, disputes by reason, and unresolved settlement differences. Compare them by destination and product type. A gateway change will not solve a supplier that repeatedly ships the wrong variant; the payment data should help locate that operational problem.
Sources and verification links
Operational rules can change. Check the linked primary sources and confirm shipment-specific requirements before booking.