Skip to main content
NewChargeback Protection + Fee Intelligence for high-volume merchants. Get a savings analysis and a review of your dispute handling.See how it works
Details

Chargeback Protection + Fee Optimization

See how it works: high-volume merchants get automated dispute evidence, interchange optimization, and real-time savings visibility.

See how it works

Launch secure online checkout without building payments from scratch

Accepting payments online starts with choosing where the card is entered, because that sets the build effort and the compliance scope. RapidCents offers a branded hosted checkout page, a payment link, or embedded fields and the gateway API inside your own checkout, with 3-D Secure applied by rule. For businesses in Canada, confirm methods and currency.

  • Canadian specialists
  • Interchange-plus available
  • Guided migration
  • Post-launch support

Who this solution is for

  • Counter businesses adding e-commerce

    The card is no longer present, which changes interchange, fraud exposure and who carries liability on a disputed order.

  • Service businesses collecting deposits

    A quote accepted online, a deposit collected before work starts, a balance taken later.

  • Teams choosing an integration path

    Hosted, embedded or API: three different amounts of work, and three different compliance positions.

Common challenges

  • PCI scope follows the card data

    A checkout that touches the card number puts your servers in scope. Hosted pages and embedded fields keep the entry surface on RapidCents, which is what keeps the assessment small.

  • Card-not-present disputes land on you

    Without authentication, fraud liability for an online order generally sits with the business. That is what 3-D Secure changes, and only where its rules apply.

  • Order state driven by the browser

    A customer who closes the tab after paying never returns to your success page. If the order only updates on redirect, that payment is invisible.

The RapidCents approach

  1. Decide where the card is entered: a hosted page, embedded fields inside your own checkout, or a payment link.

  2. Drive order state from the webhook rather than the redirect, so a closed tab does not lose a paid order.

  3. Set 3-D Secure rules by amount, geography or risk signal instead of authenticating every sale.

  4. Test in the sandbox — approval, decline, refund and the authentication challenge — before production credentials are issued.

  5. Reconcile the first online deposits against orders before any previous route is retired.

Recommended capabilities

  • Hosted checkout

    A RapidCents-hosted payment page carrying your logo, accent colour and receipt footer, with wallet buttons on supported browsers and session expiry on abandoned carts.

  • Payment links

    A pay-by-link URL sent by email or SMS, with partial amounts for deposits, custom references for reconciliation and deactivation once paid.

  • Gateway API

    Authorize and capture as separate steps for ship-later orders, customer tokens for repeat purchases, idempotency keys and signed webhooks.

  • 3-D Secure

    Issuer authentication triggered by rule. Most authentications complete without a challenge screen, and where one succeeds and network rules apply, fraud chargeback liability moves to the issuer.

  • Tokenization

    The card number is replaced by a token at capture, so your systems hold a reference that cannot be used anywhere else.

Implementation approach

  • Integration planning

    Map your checkout experience to a hosted, embedded or API approach. The decision is mostly about how much of the interface you need to own.

  • Sandbox certification

    Complete the test cases for the flows you will run, refunds and the authentication challenge included.

  • Webhook setup

    Configure and verify the events that drive order state, and confirm your endpoint rejects an unsigned request.

  • Go-live checklist

    Authentication rules, receipt content and support contacts confirmed, then live traffic monitored through the first settlement cycle.

What does not change

  • Your storefront

    Hosted checkout is a step in the flow, not a replacement for your site. Customers return to your pages afterwards.

  • Your in-person setup

    Adding online acceptance does not change the terminals at the counter. Both channels report into the same dashboard.

  • Your PCI responsibility

    Hosted pages and embedded fields reduce what is in scope. Annual validation on the questionnaire matching your integration remains yours.

Cards, currencies and settlement in Canada

What a RapidCents account in Canada accepts, the currencies it settles in, and when the money arrives.

  • Cards and methods accepted

    Visa, Mastercard, American Express, Discover, UnionPay and Diners Club cards from any country, plus Interac Debit, Apple Pay, Google Pay and EFT/PAD bank payments, on one merchant account.

  • 137+ currencies, settled in CAD or USD

    Process in CAD, USD, EUR and 137+ currencies, and deposit payouts directly into your Canadian CAD bank account or your Canadian USD bank account, so USD sales are not converted twice.

  • Next-business-day funding and reconciliation

    Batches close nightly and deposits arrive the next business day, based on cut-off times and eligibility, with deposit-level reporting in one RapidCents dashboard.

Frequently asked questions

Do I need a developer?

Not for payment links or a hosted page reached from an existing site. You do for an embedded checkout or an API integration, because order state, refunds and webhook handling are code.

Why is my online rate higher than my counter rate?

Because interchange depends on how the card was presented. A card-not-present transaction carries higher interchange than the same card tapped at a terminal, since the risk profile of the transaction is different.

Should I turn on 3-D Secure for everything?

Applied to every sale, authentication costs conversion. Applied by rule — above an amount, from certain geographies, on risk signals — it protects the transactions where the liability shift is worth the extra step.

When do online payments reach my bank?

Batches settle and eligible accounts fund next day. Online and in-person volume appear on the same deposit report.

What happens if a customer disputes an online order?

The dispute arrives with a deadline and a reason code. Transaction and authorization detail is assembled for the response, and delivery or service evidence is what you add. Whether liability sits with you depends in part on whether the transaction was authenticated.

Can I take an online payment without a website?

Yes. A payment link or a hosted payment page can be sent directly to a customer, which is often enough for a service business that quotes and invoices rather than selling from a catalogue.

What is the difference between a hosted page and embedded fields?

A hosted page is a RapidCents page the customer is sent to, carrying your logo and accent colour; embedded fields sit inside your own checkout and take your styling. In both cases the card is entered on a RapidCents surface, which keeps it off your servers.

Can I charge the card when the order ships rather than when it is placed?

Yes. The gateway API treats authorization and capture as separate steps: the funds are held at order time and taken when the goods leave. For anything shipped later, that keeps a refund from standing in for an order that never went out.

What should we test before taking live online payments?

Every flow you plan to run, in the sandbox and before production credentials are issued: an approval, a decline, a refund and the authentication challenge. Your webhook endpoint is also checked to confirm it rejects an unsigned request, and live traffic is monitored through the first settlement cycle.

Take the next step

Talk to a RapidCents specialist

RapidCents Fee Check reads a processing statement and shows interchange separately from the markup. Upload a statement for an instant breakdown, or open a merchant account and start accepting payments on one account.

  • No obligation
  • Canadian payment specialists
  • Secure statement upload