Hosted checkout FAQs

Hosted checkout is a Pine Labs managed payment page. You redirect customers to this page (or embed it in an iFrame), and Pine Labs handles the entire payment experience — payment method selection, card input, UPI, OTP, offers, and more.

No. Pine Labs handles all payment data collection and storage. You never touch sensitive card data.

Cards (Visa, Mastercard, RuPay — credit and debit), UPI (Collect and Intent), Net Banking, Wallets, Credit EMI, Debit EMI, BNPL, and Reward Points.

Yes. Use the Pine Labs Web SDK, Android SDK, or iOS SDK to integrate Hosted checkout in mobile applications.

Use the Generate Checkout Link API (POST /api/checkout/v1/orders). This creates an order and returns a redirect_url for the checkout page.

Both use the same API. In REDIRECT mode, the customer navigates to a full-page Pine Labs checkout. In IFRAME mode, the checkout is embedded inside an iFrame on your page. Set integration_mode to REDIRECT or IFRAME.

Yes. Change the integration_mode value in your API request. No other changes needed.

The payment may still complete on Pine Labs' side. Configure webhooks to receive server-to-server payment status updates regardless of customer browser behavior.

Yes. Always verify the SHA256 HMAC signature on the callback to confirm the data is authentic and untampered. See Signature Verification.

Yes. You can add your logo and configure brand colors. Contact the Pine Labs onboarding team for branding setup.

Yes. Use the allowed_payment_methods array in the Generate Checkout Link API to specify which methods to show. Omit the array to show all enabled methods.

Yes. Pass customer email_id, first_name, last_name, mobile_number, and address details in the purchase_details.customer object.

Yes. Use the purchase_details.cart_details.cart_items array to show product names, images, quantities, and prices.

Yes. Set express_checkout_enabled: "TRUE" in the merchant_metadata object. Returning customers see auto-filled addresses and saved payment methods.

Set pre_auth: true in the API request. The payment is authorized but not captured. Once you're ready to settle (e.g., after shipping), call Capture Order. To void, call Cancel Order.

Pre-authorization is available for card payments only through Hosted checkout.

Authorization holds typically last 7 days, depending on the issuing bank. Capture or cancel the order before the hold expires.

ORDER_AUTHORIZED when payment is authorized. ORDER_PROCESSED when you capture.

Shopify, WooCommerce, Magento, and OpenCart. See Ecommerce Plugins.

Web SDK, Android SDK, and iOS SDK. See SDKs.

Yes. See Hosted Checkout on Shopify.

Use the UAT environment (https://pluraluat.v2.pinepg.in) with test card details.

UPI payments process real transactions even in UAT. Test with minimum amounts (₹1).

Credit/Debit Cards, Net Banking (via SBI), Cross-Border, and Pay by Points. UPI processes real transactions.

After UAT sign-off. Share your callback and webhook URLs with the integration team for whitelisting before going live.

The callback redirect depends on the customer's browser. Always configure webhooks as the primary mechanism for payment confirmation.

Ensure you're: (1) sorting callback parameters alphabetically by key, (2) joining with &, (3) using HmacSHA256 with the correct secret_key, and (4) comparing the result in uppercase.

This is a transient error from the payment processor. Retry the payment. If persistent, contact support.

For integration support: pgintegration@pinelabs.com. For general support: pgsupport@pinelabs.com.