Overview
Integration Overview
Before you start using online payments, review the online payment documentation to understand our basic integration process. After onboarding is completed, choose the most suitable path based on launch speed, page control needs, technical resources, and compliance requirements.
PingPong Checkout provides hosted checkout, component-based SDKs, API Only, and no-code collection options. You can either let PingPong host the main payment experience or build your own page and continue the payment flow through server-side APIs.
Integration Options
Quick Launch
No-code solutions
Best for merchants without an engineering team, or for teams that want to start collecting payments quickly through links, site builders, and plugins.
- No need to build your own payment page
- Supports payment links, SaaS platforms, and plugins
- Well suited to remote payment collection and platform-based storefronts
Redirect Checkout
Fastest pathHosted payment page
Best for merchants who want to go live quickly with web checkout and accept that shoppers are redirected to a PingPong-hosted payment page.
- Minimal integration effort
- Merchant controls which payment methods are shown
- The shopper leaves the merchant page to complete payment on PingPong Checkout
Checkout SDKs
Balanced experienceEmbedded SDK / OnePage Checkout / Element SDK / Native app guides
Best for teams that want shoppers to stay on the merchant site or inside the merchant app, while combining standardized checkout capabilities with flexible page design.
- Supports in-site display of payment methods and reusable components
- Balances launch efficiency, shopper experience, and customization
- Suitable for Web, WAP, native apps, and custom page layouts
API Only
Advanced pathInternational cards / Local payments
Build your own payment page and continue the payment flow through server-side API calls. This path gives you the most control over the UI and shopper journey, but also requires the highest engineering investment.
- Merchant builds the payment page and interaction flow
- Server-side APIs create and continue payment
- International card scenarios usually require PCI DSS qualification
Quick Reference
| Integration | Best For | Effort | Control | PCI | Docs |
|---|---|---|---|---|---|
| ↗️ Redirect | Fastest go-live, zero frontend | Low | Low | Not Required | View |
| 🖼️ Embedded SDK | In-site unified payment list | Medium | Medium | Not Required | View |
| 📄 OnePage | Standardized component checkout | Medium | Medium | Not Required | View |
| 🧱 Element SDK | Deep frontend customization | High | High | Not Required | View |
| 📱 Native SDK | iOS/Android bottom-sheet payment | Medium | Low | Not Required | View |
| 💳 S2S | Full custom, complete control | High | Highest | Required | Card · APM |
| 🔗 Payment Link | Remote payment without website | Low | Low | Not Required | View |
| 🏪 SaaS / Plugin | No-code quick integration | Low | Low | Not Required | Platforms · Plugins |
Detailed Comparison
| Criteria | CheckoutRedirect Checkout | CheckoutEmbedded SDK | CheckoutOnePage Checkout | CheckoutElement SDK | CheckoutNative SDK | CustomS2S | No-codePlugins / Platforms / Pay By Link |
|---|---|---|---|---|---|---|---|
| Integration Complexity | Easy | Minimal Development | Minimal Development | Medium Development | Minimal Development | Deep Integration | Easy |
| Page Customization | Low | Medium | Medium | High | Low | Highest | Low |
| Mobile Support | Responsive Page | Responsive Page | Responsive Page | Responsive Page | Native Bottom Sheet | Responsive PageNative Page | Responsive Page |
| Redirect Mode | Required | Not Required | Not Required | Not Required | Not Required | Not Required | Depends on Scenario |
| PCI Requirements | Not Required | Not Required | Not Required | Not Required | Not Required | Card RequiredAPM Not Required | Not Required |
| Risk Control Component | Not Required | Not Required | Not Required | Not Required | Not Required | Card RequiredAPM Not Required | Not Required |