Integration

Adding Scalapay through Adyen

For enterprise and multi-region setups already running on Adyen, adding a pay-later option is handled through your existing payment method configuration.

Customer Area
Enable route
Multi-region
Supported
Test
Before live
Existing
Settlement flow
Setup on Adyen4 steps
Request the payment methodCustomer Area
Configure your merchant accountPer region
Handle the redirectIn your integration
Reconcile settlementsNormal reports
Changes to your settlement
None
SAME REPORTING FLOW
Setup

Getting live on Adyen

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

1

Request the payment method

Add Scalapay to your enabled payment methods through your Adyen Customer Area.

2

Configure per merchant account

Enterprise setups usually run several merchant accounts. Each one is configured separately, per region and per storefront.

3

Handle the redirect flow

Scalapay is a redirect method. Your integration needs to handle both the return and the abandonment path.

4

Add on-site messaging

Place the installment message on product and cart pages, not only at the payment step.

Worth knowing

Six things specific to Adyen

The details that cause support tickets if you skip them.

Multi-region rollouts

Enable per merchant account rather than globally. Availability and order limits differ by market.

Notification webhooks

Use Adyen notifications to confirm the payment result rather than depending on the shopper returning to your site.

Order limits

Orders run from $200 to $5,000 in the US. You can set a narrower range per storefront.

Refunds

Issue refunds through your normal Adyen flow. We reconcile and adjust the customer plan. How refunds work →

Reconciliation

Scalapay transactions appear in your existing settlement reports alongside other methods.

In-store

Physical retail runs through an in-app barcode or tap-to-pay rather than through terminal hardware.

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

Adyen integration FAQ

What developers and store owners ask before starting.

Can I add Scalapay to an existing Adyen setup?+
Yes. It is requested and enabled through your Adyen Customer Area and configured against your merchant accounts.
Does it support multiple regions?+
Yes, but enable it per merchant account rather than globally, because availability and order limits differ by market.
How is the payment result confirmed?+
Through Adyen notifications. Do not rely on the shopper returning to your confirmation page as the only signal.
Does it change my settlement reporting?+
No. Scalapay transactions appear in your existing settlement reports.
How are refunds processed?+
Through your normal Adyen refund flow. We reconcile the transaction and adjust the customer plan.
Does it work in physical stores?+
Yes, through an in-app barcode or tap-to-pay rather than terminal hardware.
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