DTCPay is PlatformDTC’s shopper wallet. When a shopper pays, DTCPay saves their contact details, shipping address and — if they typed in a card — that card, unless they press Not now. The next time they check out on your store, or on any other PlatformDTC store that uses DTCPay, checkout opens with everything filled in, and with one Pay with DTCPay button when a card is saved.
DTCPay is rolling out in phases, starting as a controlled test on selected stores. See Rollout and the safety switch.

​
What DTCPay saves

  • Contact details and address, for every payment method. The shopper’s email, phone number and shipping address, whether they pay by card, Apple Pay, Google Pay or PayPal.
  • Cards only when typed in. A credit or debit card typed in at checkout is saved too, on stores where card tokenisation is on for that checkout (see Rollout). Apple Pay, Google Pay and PayPal are never saved, are unchanged, and are still offered at checkout next to DTCPay.
  • Card data stays with our payment processor. PlatformDTC keeps the card’s brand, last 4 digits and expiry date so the shopper can recognise it. The card number is stored by our payment processor, never by PlatformDTC or by your store.
A DTCPay payment is a card payment on PlatformDTC Payments. It is charged at your plan’s card rate (see Payment fees and rates), is paid out with your other payments, and goes through the same fraud checks as a card the shopper types in, including your Require 3D Secure on risky card payments rules.

​
How shoppers enrol

Enrolment is automatic, with an opt-out, the same pattern as Shop Pay:
  1. At checkout. Just before the Pay button, after the payment methods, checkout shows Save my information for a faster checkout with this line, for every payment method:
    By paying, you agree to create a DTCPay account subject to DTCPay’s Terms and Privacy Policy
    “Terms” and “Privacy Policy” link to the DTCPay Terms and the Privacy Policy. A Not now button on the same row opts the shopper out for that checkout. Shoppers DTCPay already recognises don’t see the row.
  2. After the payment succeeds. Unless the shopper pressed Not now, their DTCPay account is created automatically with their contact details, address and, for a typed card, that card. No code is needed on the device they paid from; the card’s bank may ask for its own verification (3D Secure).
  3. Welcome email. The shopper gets a welcome email showing what was saved (for example Visa •••• 4242) and a Didn’t create this? Remove it link that removes it in one click.
Protecting existing accounts. If the email already has a DTCPay account with a saved card, a new card is added only from a device that account already recognises. Otherwise nothing is added from that payment. PlatformDTC records each consent with the time, IP address, browser and the version of the text shown (dtcpay-consent-2026-09-28-auto). The full terms are at platformdtc.com/legal/dtcpay.

​
The DTCPay app on the thank-you page

After every paid order, whatever the payment method and whether or not the shopper enrolled, the thank-you page shows Track your order in the DTCPay app — “Get delivery updates on your phone” — with a Get the app button. It opens that order’s tracking page at pay.platformdtc.com, where the shopper can add the DTCPay app to their home screen and turn on delivery notifications. Tracking the order doesn’t need a DTCPay account. In in-app browsers (Instagram, Facebook), where apps can’t be installed, the button just opens the order’s tracking page. Show or hide it in the Checkout Editor on the Thank you page (the DTCPay app block), or turn it off store-wide in your DTCPay settings.

​
What returning shoppers see

  • On the same device. A shopper whose account was created or confirmed on this device lands on checkout with their email, address and shipping method filled in, and — if a card is saved — one Pay with DTCPay button. The device is remembered for one year on the checkout’s own website address.
  • Every purchase needs a tap. DTCPay never charges a shopper automatically. The one tap on Pay with DTCPay is the confirmation. The card’s bank can still ask for 3D Secure on any payment.
  • Not you? Checkout shows Not you? next to the saved details. It signs this device out of DTCPay and returns to a normal checkout.
  • On a new device, or on another store. The shopper enters their email and confirms with a 6-digit code or a passkey, then checks out with their saved details.
  • Other ways to pay stay. Apple Pay, Google Pay and PayPal are still shown, in the same place.
  • Buy with DTCPay on product pages. When the option is on, shoppers your checkout already recognises see Buy with DTCPay on your product pages. It opens checkout with their details filled in and the Pay button ready; they still tap to pay. Shoppers who aren’t recognised don’t see the button.

​
Settings

Open Settings → Payment provider and find the DTCPay card.

​
Rollout and the safety switch

For a card to be saved with DTCPay after a purchase, checkout first has to save the card securely on PlatformDTC Payments before charging it. This is card tokenisation, and PlatformDTC switches it on store by store:
  • Off — checkout takes cards exactly as before. Typed cards aren’t saved with DTCPay on your store; contact details and addresses still are.
  • Split test — half of your checkouts use tokenisation and half don’t, so the two can be compared on real payments.
  • On — every card checkout uses tokenisation.
A card saved on PlatformDTC Payments this way is kept only if the shopper is saved with DTCPay. If they pressed Not now, it is removed once 7 days have passed. The safety switch. During a split test, PlatformDTC compares the two halves every minute once each has at least 300 card attempts in the last 24 hours. If the tokenised half is worse by more than 2 percentage points on decline rate, 3D Secure challenge rate or payment error rate, or its typical time to pay is more than 800 ms slower, tokenisation turns Off for your store automatically and our team is alerted. It stays off until PlatformDTC turns it back on. Shoppers who already saved their details keep them when tokenisation is off, and are still recognised on your store while DTCPay is on.

​
Orders and analytics

  • Orders. An order paid with DTCPay shows DTCPay as the wallet on the order page. The payment provider is PlatformDTC Payments, as for any card payment.
  • Analytics → Payments has a DTCPay section:
    • Enrolment rate — of checkouts that showed Save my information for a faster checkout, how many ended with the shopper saved (they didn’t press Not now).
    • Recognised checkouts — checkouts where DTCPay recognised the shopper.
    • Conversion of recognised shoppers compared with guests who typed a card.
    • DTCPay app — installs, install rate from the thank-you page’s Get the app, and orders with delivery notifications turned on.
    • Share of card payments paid with DTCPay.

​
Eligibility

  • Your store takes card payments with PlatformDTC Payments.
  • DTCPay isn’t available on a store that takes cards through its own Stripe account (Stripe Card in your payment settings). That account is separate from PlatformDTC Payments, so cards saved with DTCPay can’t be charged on it.
  • DTCPay saves cards only. Apple Pay, Google Pay, PayPal and pay-later methods work as before.

​
What shoppers control

At pay.platformdtc.com a shopper can:
  • see, set as default and remove saved cards — a removed card can’t be charged again through DTCPay,
  • see the devices where DTCPay remembers them, sign one out, or sign out everywhere,
  • see their orders from every store that uses DTCPay,
  • delete their DTCPay account, which removes every saved card and withdraws their consents. Their order history with your store is kept.

​
FAQ

No. Every DTCPay payment starts with the shopper pressing Pay with DTCPay at checkout. Renewals of a subscription the shopper signed up for are charged the same way as any card subscription.
No. Those stay on your checkout exactly as they are. DTCPay gives shoppers who type in a card a one-tap checkout the next time.
No. Your store sees the card brand and last 4 digits on the order, as for any card payment. The card number is held by our payment processor.
Yes, after they confirm a 6-digit code or passkey on your checkout. DTCPay remembers each device on each checkout website address separately, so a device remembered on another store isn’t recognised on yours until the shopper confirms once.
No. The checkout shows “By paying, you agree to create a DTCPay account subject to DTCPay’s Terms and Privacy Policy” before the Pay button, for every payment method, with a Not now button that opts out. A shopper who pays without pressing Not now gets a DTCPay account with their contact details, address and, if they typed one in, their card, and a welcome email with a Didn’t create this? Remove it link. It never charges anyone: every later purchase still needs their tap.
A card is added automatically only when that email has no DTCPay account yet, or from a device the existing account already recognises. The welcome email goes to the email owner, who can remove the card in one click.
Yes, unless they press Not now — with their contact details and address only. Wallets and PayPal are never saved. Next time checkout fills in their details and they pay with any method as usual; the one-tap Pay with DTCPay button appears once a typed card is saved.
No. Saving happens at checkout. The thank-you page’s only DTCPay element is Track your order in the DTCPay app, shown after every paid order, and the order confirmation email carries no DTCPay link.
No. It is set by PlatformDTC while DTCPay rolls out, and the safety switch can turn it off automatically. The other DTCPay settings — DTCPay on your store, the DTCPay app offer on the thank-you page and Buy with DTCPay on product pages — are yours to change at any time.
Checkout shows no DTCPay row, no new DTCPay accounts are created on your store, and shoppers can’t check out with DTCPay there. Orders already paid are unchanged, and shoppers keep their saved details for other stores until they remove them.