Skip to content
Trustfac
Apply

Payment processing for online stores that have outgrown their first checkout.

Trustfac runs the checkout on your own domain, holds every card in a vault, screens each order for fraud before it is charged, and handles subscriptions, one-click upsells and disputes on the same ledger. The integration is one package and a set of webhooks. The rest is done by people whose names you will know.1

Apply for an accountContact sales

Business accounts only. Every account is reviewed before it opens.3

The owner of a small online business taping a shipping box closed at a wooden packing table.
Accepted
Visa, Mastercard, American Express, Discover, Apple Pay, Google Pay and ACH
Integration
Hosted checkout, WooCommerce, Shopify, or the API with hosted card fields
Payouts
Daily or weekly, to a bank account in the business’s own name
Review
Two to five business days, with a person on the phone throughout

Who we work with.

Most of the stores we take on are a few years in. They sell something people reorder, they have moved past the point where a hosted checkout from their store platform was enough, and they have started to feel the costs that come with volume: a dispute ratio that someone now watches, fraud that a plugin catches after the charge rather than before it, renewals that fail quietly, and an upsell that would work if it did not require a second checkout.

We are a payment platform in the payment-facilitator model. Each business on it is the merchant for its own sales, is reviewed and approved on its own, and is paid out to a bank account in its own name. We hold the card data, run the screening, file the dispute responses and provide the dashboard; the acquiring banks and payment processors behind us settle the funds. That arrangement is why review takes a few days and why we ask for documents once, up front, rather than after the first chargeback.

It is not a fit for everyone. We do not open personal accounts, we do not process for a business other than the one that signed, and the acceptable use policy is enforced during review rather than after the fact. If that describes a store you run, the application takes about five minutes.

What the platform does.

Four services, each with its own page. They share one card vault, one customer record and one statement, so a renewal, an upsell and a refund all appear on the same ledger as the original order.

Two colleagues standing at a desk reading a document together.

Fraud prevention

Every order is scored before the card is charged, using velocity across card, device, IP address and email, the device fingerprint and IP reputation, and a list of cards and emails that have appeared in disputes anywhere on the platform. A high score is stepped up to 3-D Secure or declined; a low one goes through without the shopper noticing anything. The score, the signals behind it and the decision are kept with the order, which is what a dispute response is later built from.

Read about fraud prevention
The owner of an apparel business folding garments at a table in front of clothing racks.

Subscriptions

Recurring billing runs on the card already in the vault, on weekly to yearly periods, with the terms shown where the card is entered rather than behind a link. When a renewal fails it is retried at three, seven and fourteen days, and the customer gets a link to update the card without writing to you. A chargeback pauses the subscription on its own. Customers can skip a cycle, pause or cancel themselves, and the cancellation is confirmed by email.

Read about subscriptions
A woman at a kitchen table opening a plain cardboard parcel, with a second small box beside it.

One-click upsells

After the order is paid, the thank-you page can show one more offer, priced below the order and open for ten minutes. The shopper confirms it with the card’s security code and it is charged to the vaulted card on its own line, with no second checkout and no card to re-enter. The add-on is reported separately so you can see what the offer earns, and it carries the same refund and dispute rules as any other order.

Read about one-click upsells
A man lifting a parcel from a shelf in a small fulfilment room.

Payments and payouts

Card, wallet and bank payments are taken on your own domain, and every card is tokenized in a PCI DSS Level 1 vault before it reaches anyone’s server. Settlement goes to the business’s own bank account daily or weekly, and each payout is itemized to the order. Your statement descriptor is printed at checkout and on the confirmation, the billing address is collected separately from shipping and checked against the card, and a declined charge is explained to the shopper rather than quietly retried.

Read about payments and payouts

Every account also gets payment health, which shows which orders are unpaid and why each card was declined, customer messaging for order updates and declined-card follow-ups with consent recorded, and invoices and payment links for phone and wholesale orders. None of these needs a separate integration.

What your customers see.

A checkout page on your domain, in your name. The card fields are hosted by the vault; everything around them is yours.

Statement line
Your statement descriptor is printed at checkout and on the confirmation, so the charge is recognized later.
Billing address
Collected separately from shipping and checked against the card.
Refund terms
Shown beside the pay button and confirmed with a checkbox that is never pre-ticked.
Declines
Explained in plain language, and never retried without the customer.
LLantern Roasting Co.
lanternroasting.com
Order summary
  • Ethiopia Guji Natural12 oz · whole bean$21.00
  • House Espresso2 lb · whole bean$38.00
Shipping
$4.00
Total
$63.00
Apple PayGoogle Pay
or pay with card
4242 4242 4242 4242
08 / 29
•••
Billing ZIP · 78704
Pay $63.00

Your statement will show TRUSTFAC. Refunds within 30 days; see policy.

Example checkout and amounts

The integration.

On WooCommerce or Shopify the plugin does the work: install it, paste the keys, and the checkout, subscriptions and the upsell offer are available from the store’s own settings. On a custom store, one package mounts hosted card fields on your page and returns a token. Your server sends the token with an idempotency key, and signed webhooks report every payment, refund, dispute, renewal and payout.

Because the card number is tokenized on the customer’s device, neither your page’s code nor your server ever sees it, and your PCI scope stays at the shortest questionnaire, SAQ A. Every account starts in test mode with test cards. Live mode is switched on by our team after review, never by an API call.

Read the developer documentation
checkout.jsExample
import { Checkout } from "@trustfac/checkout";

// Card fields render inside hosted iframes on your page.
const checkout = await Checkout.mount("#card", { session });

// Tokenized on the customer's device. Your code and your server
// only ever see the token, the last four and the brand.
const { token } = await checkout.tokenize();

await fetch("/api/orders/pay", {
  method: "POST",
  headers: { "Idempotency-Key": orderId },
  body: JSON.stringify({ orderId, token }),
});

How an account is opened.

Approval is a review, not a form. These are the four stages, what each involves and what each usually takes.

  1. Step 1About five minutes
    Application

    Where the store is, what it sells, roughly what it processes, and who we are talking to. Submitting it does not open an account; it asks us to look.

  2. Step 2Two to five business days
    Review

    State registration, the EIN, the owner’s identity, sanctions screening, a read of the website, and processing statements if the store has them. We ask for the documents once, up front.

  3. Step 3The same week
    Agreement and setup

    The service agreement arrives with every fee written in. Once it is signed, checkout, the vault and payouts are set up on your domain in test mode, and the fraud rules are tuned to your order mix.

  4. Step 4After your sign-off
    Live

    Our team switches live payments on after you have tested. Subscriptions and upsells are turned on store by store, once their terms are on the page.

Pricing.

Three lines of billing. Processing is quoted after review, and every other fee is listed on the pricing page before anything is signed.2

See every fee
Processing
Quoted after review
A per-transaction rate for cards, wallets and ACH, set during review and stated in your agreement before you sign.
Platform
One monthly fee
Dashboard, checkout, fraud screening, subscriptions, upsells, reporting, dispute handling and the team that runs it. Billed monthly in advance.
Messaging
Per message, or a share of recovered sales
No setup fee. Refunded orders are not counted.

Security and compliance.

Card data never touches your server or ours. Every account is reviewed before it goes live, and every change on the platform leaves a record.

SecurityCompliance
Card data
Entered into hosted fields and held in a PCI DSS Level 1 vault. Full card numbers never reach your server or ours.
One business per account
An account processes only the sales of the business that signed for it, and pays out only to that business’s bank account.
Encryption
TLS 1.2 or newer in transit. Tax IDs, ID numbers and bank details encrypted at rest with keys held separately from the data.
Audit log
Every administrative action, pricing change and payout is written to an append-only, hash-chained log.
Review
Business verification, owner identity, sanctions screening and a read of the website before any account goes live.

Common questions.

Who is this for?

Registered US businesses that sell their own products online and have grown past a basic checkout: real order volume, repeat purchases or subscriptions, and enough fraud and disputes that they need to be handled rather than absorbed. Stores that have been turned away or priced out elsewhere because of their dispute history are welcome to apply, provided what they sell is permitted under the acceptable use policy. There are no personal accounts, and an account processes only the sales of the business that signed for it.

How is the fraud screening different from a checkout plugin’s?

It runs before the charge, on every order, and it sees the whole platform rather than one store. Velocity is measured by card, device, IP and email across all of our merchants, and a card or email that has produced a dispute anywhere is flagged everywhere. The score, the signals and the decision are stored with the order, so when a dispute arrives the response can cite exactly what was checked and when.

Can a shopper really buy an upsell without entering the card again?

Yes. The card was tokenized in the vault during checkout. The offer on the thank-you page is confirmed with the card’s security code and charged to that token on a separate line. The shopper does not see a second checkout, and your page never handles the card number at any point.

What do you need from a developer?

For a WooCommerce or Shopify store, usually nothing beyond installing the plugin and pasting the keys. For a custom store, one package mounts the hosted card fields and returns a token, your server sends that token with an idempotency key, and webhooks tell you about payments, refunds, disputes, renewals and payouts. Most custom integrations take a day; the developers page has the details.

Where does the money go?

To a bank account in the business’s own name, on a daily or weekly schedule. Every payout lists the orders and fees inside it, and the same figures appear in the dashboard and on the monthly statement.

Is a processing rate published?

No. Rates depend on volume, category, average order and history, and are quoted after review and written into the agreement before you sign. The pricing page lists every other fee, including disputes, refunds and ACH returns.

Start the application.

Two fields here, then three short steps on the next page: the store, what you need, and how to reach you. We read the store before we reply, so the first email you get from us is about your business and not a template. If you would rather talk first, contact sales.