Payment gateways and providers for DTC brands

Take cards, wallets and pay-later on your own domain, through the provider you choose. 6 providers process payments on PlatformDTC, and every one of them settles into an account you own.

Payment providers you can use

One of these handles card payments at a time, and PayPal runs alongside whichever it is. Switching is a setting rather than a migration — existing subscriptions keep renewing on the provider that first charged them.

PlatformDTC Payments

The payments account PlatformDTC opens for your store, so a new store can charge a card without sourcing a processor first.

Connecting it
Created with the store. You complete identity and bank verification in the onboarding flow, and the account is yours — payouts settle to your bank, not to PlatformDTC.
Settlement
Your own connected account. Payouts on your own schedule.

Stripe

Your existing Stripe account, used directly. The processing agreement, the rates and the payout schedule stay between you and Stripe.

Connecting it
Connect from Settings → Payments. Card charges, wallets and subscription renewals run against your account.
Settlement
Your own Stripe account, on your own Stripe pricing.

PayPal

PayPal as a checkout button and as a stored funding source for subscription renewals, running against your own PayPal business account.

Connecting it
Connect with PayPal, or paste the REST client ID and secret from an app in your PayPal developer dashboard. Turning PayPal off for new orders leaves existing subscriptions renewing on it.
Settlement
Your own PayPal business account.

Authorize.Net

A gateway-only provider: no OAuth and no marketplace, just your account and its keys.

Connecting it
Paste the API Login ID and Transaction Key from Account → Security Settings in the Merchant Interface. Card and wallet charges run against your own Authorize.Net account.
Settlement
Your own Authorize.Net account and its acquirer.

Checkout.com

A global processor, typically chosen for cross-border acceptance and scheme coverage.

Connecting it
Paste the Public Key, Secret Key and Processing Channel ID from the CKO Hub. The credentials are validated against Checkout.com before they are saved; the webhook signature key is optional but wanted in production.
Settlement
Your own Checkout.com account.

MyFatoorah

A Gulf-region provider, used where local methods and local acquiring matter more than global scheme coverage.

Connecting it
Paste the API key and select the country the account is registered in.
Settlement
Your own MyFatoorah account.

Airwallex

Connect only

Connectable from the admin, and not yet routed at checkout — an account can be linked, but card payments do not run through it.

Connecting it
Connect with Airwallex from Settings → Payments → third-party providers.
Settlement
Your own Airwallex account.

Airwallex is listed as connect-only because the account links but the checkout does not route card payments to it yet. It is here rather than omitted so the list matches what you will find in the admin.

Wallets and pay-later at checkout

These sit above the card form rather than replacing the provider behind it. Which of them a shopper is offered depends on their device, their browser and the method’s own eligibility rules.

Apple Pay
Safari and iOS, on a device with a card in Wallet.
Google Pay
Chrome and Android, and on Authorize.Net and MyFatoorah stores.
PayPal
Also the funding source for renewals when a subscription is bought with it.
Klarna
Pay-later, subject to Klarna approving the individual order.

For how the express row and the card form are laid out on the store’s own domain, see express checkout, and PlatformDTC Payments for the account behind it.

About payment gateways

Get started today

Start for free. Your first month is $1.