Payment Cascade or a direct Klarna integration?#
If Klarna is the only BNPL method you'll ever offer, integrate it directly. It's one less service between you and your customers. This page is for the moment you start thinking about a second provider, or start noticing how many customers Klarna turns down.
| Direct Klarna | Through Payment Cascade | |
|---|---|---|
| Providers | Klarna | Klarna, Riverty, Scalapay |
| Klarna declines | the customer sees an error | Riverty or Scalapay opens next |
| Webhooks you parse | Klarna's | one format for all three |
| Adding Riverty later | a new integration | paste an API key in your account |
| Your provider contracts | yours | still yours |
| Cost | developer time | €1 per paid order |
Customers still pay on Klarna's own page, and Klarna still pays out to you. We sit between your backend and the providers' APIs; payments never pass through us.
What you no longer write and maintain is the glue: the session and order calls for each provider, converting your cart and addresses into three different shapes, verifying three kinds of webhook signatures, and making sure an abandoned Klarna attempt is closed before Riverty opens, so a late approval can't charge the customer twice.
Not sure the declines are worth the trouble? Put your own numbers into the decline calculator. If the result is a few orders a month, stay with direct Klarna.