You invested in traffic, optimized the funnel, tested creatives, tuned the price. The customer arrives at checkout motivated. And then the page redirects to a domain that looks like a 2000s bank page. The URL bar changes. A weird loader appears. The customer thinks twice and abandons. Every percentage point of conversion lost at that step erased weeks of upstream optimization. BSPay Transparent Checkout removes the problem at the root: the customer never leaves your domain, UX stays 100% under your control, card data flows through PCI-compliant tokenization without hitting your server — and conversion climbs 15-25% against the traditional redirect checkout.
Transparent Checkout is the integration mode where the customer pays inside your site, without being redirected to an external gateway domain. The card, PIX or boleto form appears on your page with your product’s visual identity; sensitive data flows through a secure iframe or client-side tokenization (PCI-compliant) straight to the gateway, without touching your server. The user experiences an integrated checkout; you preserve brand, UX, analytics and — most importantly — conversion.
The opposite is “redirect checkout” or “hosted checkout”: the customer clicks Pay and gets sent to a domain like payments.somegateway.com, where they fill everything. It works, it’s simpler to integrate, but costs 15-25% conversion on average — especially on mobile, where switching domains reads as a red flag to users.
You integrate a component (web or mobile) provided by BSPay into your checkout page. That component is a secure iframe or a JavaScript library that captures sensitive data and runs client-side tokenization. The token returns to your front-end, which sends it to your backend — which calls the gateway API with the token instead of real card data. Result: integrated experience without putting your server into PCI scope.
| Aspect | Redirect checkout (hosted) | BSPay Transparent Checkout |
|---|---|---|
| Domain during payment | External (gateway) | Your domain |
| Typical conversion | Baseline | +15% to +25% |
| Brand consistency | Broken at switch | Preserved |
| Paid traffic attribution | Broken at redirect | Intact |
| Apple Pay / Google Pay | Partial | Native |
| One-click recurring | Difficult or impossible | Native via token |
| Your server’s PCI scope | None | None (client-side tokenization) |
| Integration effort | Lower (1-2 days) | Moderate (3-7 days with SDK) |
| Visual customization | Zero | 100% (your CSS) |
| Perceived latency | Redirect + load | Instant |
BSPay Transparent Checkout is free in every plan — no extra cost for processing transparent rather than redirect. The choice is technical, not financial: you integrate once, enable Elements or SDK, and the customer pays without ever leaving your domain. Gateway rate is the same (from 2.99% on card, 0.49% on PIX). Operational saving comes from the conversion you stop losing — in a typical operation at R$500k/month, a 20% conversion lift means R$100k/month more.
Typical integration in 3-7 days with SDK ready for React, Vue, Angular, iOS and Android. Dedicated implementation team, complete sandbox, WhatsApp support with engineers. See all features on the homepage or talk to a specialist to estimate how much conversion your operation gains migrating from redirect to transparent.
No. Tokenization is done client-side by the Elements (secure iframe) or mobile SDK — card data never touches your server. Your PCI scope stays zero, same as with redirect checkout. You only need your own PCI certification if you opt for Direct API (rare and requires Level 1-4 certification depending on volume).
Industry benchmark: +15% to +25% checkout conversion when the only changed variable is redirect → transparent, with the same gateway underneath. The gain is larger on mobile (up to +30%) and on high-ticket products. We run an A/B test before go-live to validate the specific impact on your funnel.
3-7 technical days with SDK and documentation. Modern frameworks (React, Vue, Angular) have a ready component that’s literally <CheckoutElement /> in your code. Mobile with iOS and Android SDK: 5-10 days. E-commerce platforms with official plugin (Shopify, WooCommerce, VTEX) go live in hours.
Yes. Official BSPay plugin for Shopify, WooCommerce, VTEX, Magento, Nuvemshop, Wake and Yampi already delivers transparent checkout out-of-the-box — no custom code. Teams with custom checkouts use Elements or SDK directly.
Yes, native in the transparent checkout. Enable via flag in the dashboard — no extra integration beyond the already integrated Elements. Apple Pay needs domain validation (5 minutes of setup via .well-known file).
No. Transparent checkout maintains 100% of your visual identity. The only BSPay reference is backend-side (logs, admin dashboard) and, eventually, in chargeback or anti-fraud communication according to card network regulatory requirements — never visible to the end buyer.
Yes. Tokenized card is saved in the BSPay PCI vault with a reference to your customer ID. Customer returns weeks later and pays in 1-click without re-entering the card. Recurrence via PIX Automático, tokenized card or debit. Webhooks inform each recurring charge to your backend.
Device fingerprint captured on your domain (more precise than on the gateway’s domain). Real-time behavior analysis. Cross-method scoring: customer tries card, gets declined, tries PIX — the system detects and adjusts the score. Plug-and-play integration with ClearSale, Konduto and Kount for teams wanting additional external anti-fraud.
