Integration

Adding Scalapay through Stripe

If you already process with Stripe, adding a pay-later option is mostly a matter of enabling it and handling the redirect properly in your existing flow.

Dashboard
Enable route
Redirect
Payment flow
Sandbox
Test first
Existing
Reconciliation
Setup on Stripe4 steps
Enable in the dashboardPayment methods
Connect your merchant accountCredentials
Handle the redirectIn your checkout flow
Reconcile in reportingNormal payouts
Changes to your payout flow
None
SAME SETTLEMENT PROCESS
Setup

Getting live on Stripe

The order below matters — messaging before testing, testing before live traffic.

1

Enable the payment method

Turn Scalapay on in your Stripe dashboard so it becomes available to your checkout.

2

Connect your merchant account

Link your Scalapay merchant account so orders and settlements reconcile correctly.

3

Handle the redirect

The customer is taken to complete approval and returned to your confirmation page. Make sure your success and cancel URLs handle both outcomes.

4

Add on-site messaging

Show the installment figure on product and cart pages, which is where it influences the decision.

Worth knowing

Six things specific to Stripe

The details that cause support tickets if you skip them.

Redirect handling matters

A customer who abandons at the approval step must land somewhere sensible. Test the cancel path as carefully as the success path.

Payment intents

Scalapay behaves as a redirect-based method, so build for an asynchronous confirmation rather than an immediate one.

Webhooks

Rely on webhook confirmation rather than the redirect alone to mark an order as paid.

Refunds

Issue refunds through your normal Stripe flow. We adjust the customer plan accordingly. How refunds work →

Reporting

Scalapay orders appear in your existing reporting alongside card payments.

Order limits

Orders run from $200 to $5,000, and you can set a tighter range for your catalogue.

Before you switch on

Test the paths that are not the happy one

Every integration works when the customer does exactly the expected thing. Problems come from the other cases.

  • A customer who abandons at the approval step — they must land somewhere sensible with the basket intact.
  • A declined order — this is a normal outcome, not an error. Send them back to a checkout with other options available.
  • A partial refund — check the customer plan recalculates and your own reporting matches.
  • An order outside the range — validate against $200 to $5,000 before showing the option, so nobody is offered something that will fail.
Test before going live4 paths
Full orderHappy path
Abandoned approvalMust test
Declined orderMust test
Partial refundMust test

Testing only the successful order is the most common reason an integration causes problems in its first week.

Questions

Stripe integration FAQ

What developers and store owners ask before starting.

Can I use Scalapay if I process with Stripe?+
Yes. It is enabled as a payment method in your Stripe dashboard and connected to your Scalapay merchant account.
Does it change how I get paid?+
No. Settlement follows your existing Stripe payout schedule.
Is it a redirect payment method?+
Yes. The customer completes approval and returns to your confirmation page, so build for an asynchronous confirmation and rely on webhooks rather than the redirect alone.
How do I test it?+
Enable it in sandbox and run a full order plus both a partial and a full refund before going live.
How are refunds handled?+
Refund through your normal Stripe flow. We reconcile the transaction and adjust the customer plan.
Do I need custom code?+
Some, if your checkout is custom. The payment method itself is enabled from the dashboard, but the redirect handling lives in your own flow.
More for business

Other integrations

Same account, different platform.

Ready to add it?

Apply for a merchant account and we will get you the credentials and the docs.

Pay in 3 · 0% interest
$200–$5,000 · no credit check
Apply Now