Overview
About 1057 wordsAbout 4 min
2025-03-07
Integration Overview
Before starting to use online payment products, you can review the online payment API documentation to get a preliminary understanding of our integration process. After onboarding is completed, you can begin the integration.
You can integrate our API interfaces in multiple ways. These range from using pre-built integrations to building your own checkout interface to completely control your checkout experience. We recommend that you make your choice based on your needs and capabilities.
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 |
How to Choose
Checkout
Redirect Checkout
Recommended For
Merchants who want to go live fastest with no frontend development. PingPong hosts the entire payment flow.
Redirect customers to the PingPong Checkout hosted page. We handle the entire payment process so you can focus on your business.
Embedded SDK
Recommended For
Merchants who want to display a unified payment method list in-site while lightly customizing the page appearance.
Display a unified list of payment methods to customers during checkout without extensive frontend development.
See Embedded SDK
OnePage Checkout
Recommended For
Merchants looking for a standardized, component-based checkout with consistent UX and lower development cost.
Use a more standardized, component-based checkout capability for better interaction consistency at a lower development cost.
See OnePage Checkout
Element SDK
Recommended For
Teams with medium-to-high frontend customization needs who want flexible component-based payment assembly.
Flexibly combine payment buttons and capabilities as components while maintaining high page customization space.
See Elements SDK
Native SDK
Recommended For
Mobile app developers — integrate a bottom-sheet payment experience in approximately 20 lines of code.
Integrate a bottom-sheet payment experience in iOS/Android apps. Users complete payment without leaving the current page.
See Native SDK
Custom Integration
S2S
Recommended For
Teams with full control needs and sufficient development resources. Note PCI compliance requirements.
Build transactions directly using our API on the backend for complete control over the checkout page appearance and user experience.
See Card Payment (S2S), Local Payment (S2S)
No-Code Integration
Payment Link
Recommended For
Scenarios without a standalone website or requiring remote payment collection — accept payments via a link.
Embed or share a link to the PingPong Checkout payment page to accept payments without a website.
See Payment Link
Platform or Plugin Integration
Platforms
For more platform support, see SaaS Website Building Platforms
Plugins
For more plugin support, see Plugins





