If you have never accepted an online payment before, the volume of jargon can feel intentional. It is not — it is just historical. Here is the full picture, in the order you will actually encounter each piece.
Step 1: Decide what you are selling
Different products have different payment patterns. A one-time digital download is the simplest. A physical product is more involved (shipping, fulfillment proof, returns). A subscription needs recurring billing. A marketplace where one customer pays another adds connected accounts to the mix. The choice shapes your processor selection more than any other factor.
Step 2: Pick a processor
For a brand new business, the choice is almost always between Stripe, PayPal, Square, or a platform built on top of one of those (like Cenoa Pay). The right answer is whichever one ships the payment methods your customers actually use, in the country your business is based in. Resist the urge to optimize for fees in the first three months; you do not yet know what you are optimizing.
Step 3: Set up the account
Expect to provide:
- Your legal business name, type, and address.
- Tax ID (EIN in the U.S., VAT ID in Europe).
- A government ID for the account owner.
- The website or social media presence where the business operates.
- A bank account to receive payouts.
Most modern processors approve in minutes if your documents are clean.
Step 4: Add a payment method to your site
Three options, in increasing order of effort:
- Hosted checkout. A button on your site redirects to a processor-hosted page. Easiest, lowest customization.
- Drop-in components. Embedded card fields hosted in an iframe by the processor. Good visual control, almost no PCI burden.
- Custom UI on a payments API. Full control, full responsibility for PCI and fraud.
For a first launch, use hosted checkout or drop-in components. You can graduate to custom later.
Step 5: Set up webhooks
Configure a single webhook endpoint to receive event notifications from the processor. Subscribe to at minimum: payment_intent.succeeded, payment_intent.payment_failed, charge.refunded, charge.dispute.created. Each event should update the matching order in your database.
Step 6: Test the unhappy paths
Use the processor's test cards to simulate:
- A successful charge.
- A declined card.
- A fraudulent charge.
- A 3D Secure challenge.
- A refund.
- A dispute.
If any of these break, fix them before launch. They will happen in production within the first week.
Step 7: Launch and monitor
Watch your first 24 hours of live transactions closely. Look for:
- Unexpected declines (often AVS/CVV configuration).
- Customers stalling on the 3DS prompt (often misconfigured).
- Unfamiliar payouts on your processor dashboard (often a config mismatch).
Most issues that bite a new merchant show up in the first few days, when the volume is small enough to investigate every transaction.
Common pitfalls
- Going live with test API keys still in production. Triple-check.
- Forgetting to enable Apple Pay and Google Pay. They lift mobile conversion 20-30%.
- Not adding a clear refund policy to your checkout. Disputes spike without it.
- Treating every refund as a manual support ticket. Build a self-serve refund flow as soon as you have any volume.
How Cenoa Payment Helps
Cenoa Payment was built to remove the friction this article describes. Whether you are a freelancer collecting your first international invoice or a fast-growing merchant accepting payments in dozens of currencies, Cenoa gives you wallet, checkout, and payouts under one roof — backed by regulated payment and banking partners.
- Open a multi-currency wallet in minutes, no minimum balance.
- Accept cards, Apple Pay, SEPA, iDeal, bank transfers, and crypto from 195 countries.
- Pay and get paid by username, link, or QR code — no IBAN gymnastics.
- Real-time fraud and KYC tooling so your account stays in good standing.
If you are evaluating processors, sign up for free and try a real transaction end-to-end. Most teams know within an hour whether Cenoa fits their workflow.