Payment Processing for Indie Author Direct Stores

The payment processor is the part of your direct store that most authors configure during setup and then never revisit — until something goes wrong. A chargeback from a reader who claims they never received their ebook. A VAT compliance notice from a European tax authority. A reader in Germany whose preferred local payment method isn't supported. A payout delay during a launch week when you expected funds in your account.

None of these are emergencies if you've set up the payment layer correctly and understand how it works. All of them are problems if you haven't. This article covers the financial plumbing of a direct sales store: which processors to use and why, how international payments work, what VAT compliance for digital goods actually requires, when you get paid, and how to handle refunds and disputes when they arrive.

The platform-specific payment configuration — how to connect Stripe to Shopify, how to add PayPal to WooCommerce — is covered in the Shopify (DS03) and WooCommerce (DS04) articles. This article covers the financial and operational layer that sits above the platform.

The Two Processors Every Author Store Needs

Stripe and PayPal. Both. Not one or the other.

The case for offering both Stripe and PayPal: the segment of readers who will not complete a purchase without PayPal is real and measurable. It skews older and international. Adding PayPal as a second checkout option takes 15-20 minutes and adds no ongoing cost. The conversion lift from that segment outweighs the minor setup effort for virtually every author store.

The case against PayPal as your only processor: PayPal's dispute resolution process historically favors buyers, account holds are more common on new accounts with sudden sales spikes (which happen during launches), and PayPal's checkout experience is less clean than Stripe's. Use both, configure Stripe as primary, add PayPal as a secondary option.

International Sales and Currency

Your direct store is global by default. A reader in the UK, Australia, Canada, or anywhere else can find your store and attempt to purchase. How your payment processor handles their transaction determines whether they complete the purchase or abandon at checkout.

Currency Display

Shopify with its Markets feature can display prices in the reader's local currency and handle conversion at checkout. A UK reader sees £ prices; an Australian reader sees AU$ prices. This reduces the friction of readers calculating exchange rates mentally and increases conversion from international buyers.

Payhip handles multi-currency automatically — it detects the reader's location and displays prices in local currency without additional configuration. This is one of Payhip's most underappreciated features for authors with international readership.

WooCommerce requires a multi-currency plugin (WooCommerce Payments includes this natively; third-party options include WOOCS and Currency Switcher for WooCommerce) to display local currency prices. Without it, all readers see your base currency regardless of location.

Payment Methods by Region

Credit cards and PayPal cover the majority of international buyers. But specific regions have dominant local payment methods that readers in those markets strongly prefer:

For most indie authors, the standard Stripe + PayPal configuration covers 90%+ of international buyers adequately. Adding regional payment methods is worth investigating if your analytics show significant traffic from Germany, the Netherlands, or Brazil specifically — these are markets where local payment methods meaningfully affect conversion.

VAT on Digital Goods — What's Required and What Isn't Optional

If you sell digital goods (ebooks, audiobooks) to customers in the European Union, you are required to collect and remit VAT at the buyer's country rate — regardless of where you are based. This is not a threshold that only kicks in at certain sales volumes. The requirement applies from your first digital sale to an EU resident.

This sounds alarming. The practical mechanics are more manageable than the legal description implies:

Payhip — The Easiest Solution

Payhip collects and remits EU VAT automatically on all digital product sales. You don't configure anything, file anything, or think about it. Payhip handles it as part of its platform. This is the most significant operational advantage Payhip has over Shopify for authors selling to European readers, and it's one of the primary reasons to start with Payhip before migrating to Shopify.

Shopify — Requires a Tax App

Shopify does not handle EU VAT automatically for digital goods. You need a tax compliance app — TaxJar or Quaderno are the standard options. Both integrate with Shopify to calculate VAT at the correct country rate at checkout, collect it from the buyer, and generate the reports you need for filing. TaxJar also offers AutoFile in some regions, automating the remittance step. Configure this before your first sale, not after you've accumulated VAT liability.

WooCommerce — Similar to Shopify

WooCommerce has basic tax configuration built in, but EU VAT compliance for digital goods requires either the EU VAT Assistant plugin or a TaxJar/Quaderno integration. The EU VAT Assistant handles the rate lookup and collection mechanics; reporting and remittance still require attention. If your WooCommerce setup is primarily for UK and US sales, standard WooCommerce tax settings may be sufficient. If you have significant EU readership, use a dedicated VAT compliance plugin.

UK VAT Post-Brexit

The UK left the EU VAT system with Brexit. UK VAT is now separate from EU VAT. The UK's digital services VAT threshold for non-UK businesses is £85,000 in UK sales annually — below that threshold, non-UK authors are not required to register for UK VAT. This threshold is high enough that most indie authors don't reach it. Monitor your UK sales annually and consult a tax professional if you approach the threshold.

Payout Timing — When Does the Money Arrive

Refund Policy for Digital Products

Your refund policy for digital products needs to be explicit, visible, and defensible. The standard position for digital goods in direct sales: no refunds once the file has been downloaded. This is the industry norm, it's legally defensible in most jurisdictions, and BookFunnel's delivery tracking gives you documented proof of when and whether a file was downloaded.

Your refund policy should appear on your checkout page (one sentence), your Terms of Service page (full policy), and your product pages (brief statement). The full policy should specify:

• Digital products are non-refundable once downloaded or accessed

• If a file has a genuine technical defect (corrupted file, wrong format delivered), you will replace it at no cost

• For print/physical products: standard return window (typically 14-30 days) for items that arrive damaged or significantly different from description

• How to contact you for a legitimate issue: email address or contact form

A clear, reasonable refund policy reduces disputes. Readers who understand the policy before purchasing are less likely to file a chargeback when they have buyer's remorse about a digital purchase. The refund policy is also your first line of defense in a PayPal or Stripe dispute — documented policy displayed at checkout is evidence that the buyer agreed to the terms.

Chargebacks and Disputes — How to Handle Them

A chargeback occurs when a reader contacts their bank or credit card company to reverse a charge, rather than contacting you directly. Chargebacks are more serious than refund requests — they involve your payment processor, cost you a dispute fee ($15-$25 per chargeback regardless of outcome), and can affect your processor account if they occur frequently.

The two most common chargeback reasons in author direct stores:

• 'Item not received': the reader claims they never got the ebook. BookFunnel's delivery tracking — showing the exact time the delivery email was sent and whether the download link was accessed — is your documentation. Export the delivery record from BookFunnel and submit it with your dispute response.

• 'Unauthorized transaction': the reader claims they didn't make the purchase. This is harder to defend, but the purchase IP address, device fingerprint (available in Stripe's dispute tools), and delivery email record create a factual record of the transaction.

The dispute response process: both Stripe and PayPal allow you to submit evidence through their dashboards within a response window (typically 7-10 days). Submit: BookFunnel delivery confirmation, your refund policy as shown at checkout, the purchase receipt sent to the buyer's email, and any correspondence with the buyer. Stripe's dispute documentation is more author-friendly than PayPal's — Stripe provides a structured evidence submission form; PayPal's process is less clear.

Business Bank Account and Tax Recordkeeping

Every payment processor — Stripe, PayPal, Shopify Payments — pays out to a linked bank account. That account should be a dedicated business account, not a personal account. Mixing business and personal finances creates accounting problems, complicates your tax filing, and in some business structures (LLC) can compromise the liability protection the entity provides.

Open a dedicated business checking account before your first direct sale. The account doesn't need to be expensive — most banks offer free or low-cost business checking, and fintech options like Relay or Mercury offer business accounts specifically designed for small online businesses with no minimum balance requirements.

Keep records of every transaction, every payout, every refund, and every chargeback. Stripe and PayPal both export transaction histories. ScribeCount's Sales Dashboard consolidates your direct store revenue alongside your retail royalties — the combined view gives you the total income picture for tax purposes without manually assembling reports from multiple sources.

ScribeCount and Payment Tracking

Connect your direct store to ScribeCount so your Stripe/Shopify/Payhip revenue appears in the Sales Dashboard alongside your Amazon KDP royalties, Kobo income, IngramSpark print royalties, and audiobook income. For authors running both retail distribution and direct sales simultaneously, this unified view is the only practical way to understand your total author business without spending hours assembling data from six different dashboards.

The Sales Dashboard shows revenue by channel over time — letting you see whether your direct store is growing as a share of your total income, which products drive the most direct revenue, and how a direct launch compares to a retail launch for the same title. This data informs every subsequent pricing, promotion, and product decision you make.

Payment Processing Checklist

• Stripe (or Shopify Payments on Shopify) configured and tested

• PayPal added as secondary payment option

• Business bank account linked to both processors

• EU VAT configured: Payhip handles automatically; Shopify/WooCommerce requires TaxJar or Quaderno

• Refund policy written, visible at checkout, and linked in footer

• PayPal account fully verified before launch (bank linked, identity confirmed)

• Payout schedule configured in Stripe to match your cash flow needs

• Store connected to ScribeCount for unified revenue tracking

Payment processing is infrastructure — it should work invisibly in the background while you focus on writing and marketing. Set it up correctly before your first sale, understand the VAT and chargeback mechanics before they become problems, and connect everything to ScribeCount so your direct revenue is visible alongside everything else you earn.

-Randall Wood