Integration paths
Choosing the right integration path
There’s no one-size-fits-all way to integrate ekko. The right approach depends on how much control you require over the experience, how quickly you'd like to launch, and at which point in the payment journey you want to engage your customers.
Integration options at a glance
| Integration type | Timing | Effort | Best for | Use when |
|---|---|---|---|---|
| Custom API integration | Any point in the journey | High | Full control, custom flows, deeper integrations | You want flexibility and can handle the logic server-side |
| Checkout SDK | Pre-purchase | Medium | Embedded impact experience in checkout | You want to show impact directly in your checkout flow |
| ImpactPay SDK (page takeover) | Post-purchase | Medium | Full-page impact journey before redirect | You want to guide customers through a dedicated post-purchase journey |
| ImpactPay SDK (embedded) | Post-purchase | Medium | Inline component on payment confirmation page | You want a modular component inside your confirmation page that feels native to your page |
| ImpactPay URL | Post-purchase | Low | A way to offer a hosted impact journey via link | You want to link customers to a hosted experience from emails, receipts, or offline channels |
Updated 7 months ago
