Skip to main content
Place one order yourself, on your live storefront, with your own card. Everything before this step is configuration you have read back to yourself. This is where you stop reading. Pick a listing and dates that block nothing else. TWICE has no test-mode toggle for payments, so the account you are testing is the account that goes live, and you are genuinely charging and refunding a card with fees on both sides.

​
Run the round trip on the storefront

Place one order the way a customer would, and take it through a return that goes wrong on purpose. A clean return exercises the path you already trust. A damaged one exercises the money decisions you have not tested. Pay with a real, storable card and let TWICE place a real authorization before you capture against it. A deposit with no saved card is recorded rather than authorized, so capturing it is bookkeeping and proves nothing about whether a real capture works. See the deposit steps in Take payment and deposits.

​
Run it from the counter too

Run the same order a second time through Take an order in admin, the way your counter actually will, start to close. Skip the damaged return this time. The point is the path, not a second round trip. Staff take orders in admin and customers place them on the storefront. Both reach the same Order, and the two paths are not equivalent.
An order created in admin sends nobody an email by itself. The confirmation emails fire on a completed checkout, so Create Order plus Manual payment produces no customer confirmation and no receipt. Send a checkout link instead of collecting manual payment, or hand the customer a printed receipt from the order’s Documents tab.

​
Done when

  • One storefront order has been placed, confirmed by email, paid, handed out, returned damaged, charged for the damage, refunded and closed.
  • The confirmation email arrived in a real inbox, and its receipt attachment read correctly.
  • Any custom document template you rely on rendered this order’s data from the Documents tab.
  • A deposit capture moved money, because it was captured against a real authorization.
  • A counter-created order has run through the same states, and your team knows which payment methods leave a customer without an email.
  • Nothing from this round trip is sitting open in the Orders table.

Test your processes

The launch step this guide belongs to.

Take an order in admin

The counter path, in full.

Take payment and deposits

Reserving and capturing the deposit this test relies on.

Handle a return

Recording damage and charging for it.

Refund an order

Sending the money back at the end of the round trip.

Cancel or archive an order

Closing the test out so it does not linger.

Emails

The two order-confirmation templates, and where they are edited.