iFrame checkout FAQs
Frequently asked questions about Pine Labs iFrame checkout — embedding, browser compatibility, mobile support, security, callbacks, and troubleshooting.
General FAQs
1. What is iFrame checkout?
iFrame checkout embeds the Pine Labs hosted checkout page inside an iFrame on your website. The customer stays on your page and completes payment within the embedded checkout, without a full-page redirect.
2. How is iFrame checkout different from Hosted (redirect) checkout?
The only difference is how the checkout is displayed. iFrame checkout embeds the page on your site. Redirect checkout navigates the customer to a full-page Pine Labs checkout. Both use the same API — Generate Checkout Link — with a different integration_mode value (IFRAME vs REDIRECT).
3. Do I need PCI compliance for iFrame checkout?
No. Pine Labs handles all payment data collection inside the iFrame. You never touch sensitive card data.
4. What payment methods does iFrame checkout support?
All the same methods as Hosted checkout: Cards, UPI (Collect and Intent), Net Banking, Wallets, Credit EMI, Debit EMI, BNPL, and Reward Points.
5. Is iFrame checkout the same as Custom (Seamless) checkout?
No. iFrame checkout uses the Pine Labs hosted UI inside an iFrame. Custom checkout means you build your own payment UI and call Pine Labs APIs directly. iFrame requires no PCI compliance; Custom requires PCI compliance.