Shopify Checkout in Brazil: Native or Yampi and Cartpanda?

The short answer

A transparent checkout on Shopify is a payment that happens inside the store itself, without sending the customer to an intermediary's page, and in Brazil the native checkout with Shopify Payments already does that job with Pix and cards. Yampi and Cartpanda replace that checkout with their own, outside Shopify. That comes at a cost: Shopify's additional fee for third-party providers, a second subscription, the loss of Shop Pay, discounts and pixels in two places, and support split between two companies. The rule I use is simple: native as the default, external only when there is a concrete requirement the native checkout does not meet and that pays for itself. The rest of this article shows how to tell a real requirement apart from market habit.

1. What Shopify's native checkout already delivers in Brazil

The most repeated argument for installing an external checkout in Brazil comes from a time when Shopify did not handle local payments properly. Pix required a third-party gateway, installments depended on an app, and merchants solved everything at once by swapping out the entire checkout. That scenario has changed.

Shopify Payments is the platform's native processor, activated and configured in the admin itself. The help center makes it clear that methods and availability vary by country (Shopify Payments). For a Brazilian store, the check is straightforward: open Settings > Payments and see which methods appear for your account. If Pix and cards are there, the foundation of a transparent checkout is already in place without any app.

What comes with it, at no integration cost:

• A single checkout. Cart, shipping, discounts, payment and orders live in the same system. Inventory, coupons and reports speak the same language.
• Shop Pay. Shopify's accelerated checkout stores the shipping and payment details of anyone who has already bought from any store with Shop Pay, and it works inside the Shopify checkout (Shop Pay).
• Configuration in the admin. Required fields, contact method, marketing consent and appearance live under Settings > Checkout (checkout settings).
• Native conversion events. App pixels and custom pixels subscribe to checkout events through the Web Pixels API, including checkout started and purchase completed (Web Pixels API).

What you can customize without leaving the native checkout

The native checkout is not a closed box. Shopify split customization into two layers:

• Logic: Shopify Functions change back-end rules, such as discounts, the order and visibility of payment methods, and delivery options (Shopify Functions).
• Interface: Checkout UI Extensions place components in the checkout. The official documentation restricts extensions in the information, shipping and payment steps to Shopify Plus; the thank you and order status pages accept extensions on other plans (Checkout UI Extensions).

A detail that confuses people coming from themes: app blocks and app embeds are pieces of the store's theme, built for Online Store 2.0 themes (Theme App Extensions). For interface inside the checkout, Shopify's documentation covers a different tool, the Checkout UI Extensions mentioned above.

2. How Yampi and Cartpanda fit into Shopify

Yampi presents itself as a Brazilian e-commerce platform with its own checkout and integration with Shopify (Yampi). Cartpanda presents itself as a checkout platform with an upsell funnel (Cartpanda); its homepage does not detail the connection with Shopify, so that point should be confirmed with the vendor before signing up. Both have serious products and loyal users. The point here is not vendor quality. It is architecture.

When an external checkout is connected to a Shopify store, the typical flow looks like this:

1. The storefront stays on Shopify: theme, product, collection, cart.
2. When the customer clicks to check out, a script or app redirects them to the vendor's checkout.
3. Payment happens there, with the gateway configured there.
4. The order comes back to Shopify, created by an app, so that inventory, fulfillment and the ERP can carry on.

That redirect is what changes everything. The customer leaves the Shopify checkout. From that point on, what Shopify offers inside the checkout (Shop Pay, Functions, extensions, native checkout pixels) no longer applies to that purchase, and each of those pieces has to be rebuilt at the vendor or accepted as a loss.

Why the market adopted it en masse

Three reasons, and none of them is silly:

• History. When the native checkout did not handle Pix and local installments, the external checkout solved everything in one package.
• Upsell funnel. Order bumps, post-purchase offers and aggressive cart recovery came ready-made on these platforms, aimed at merchants who sell through ads.
• Word of mouth. Agencies, courses and merchant groups repeat the same stack. The decision becomes the default without anyone running the numbers.

The historical reason has lost its strength. The other two may still hold, but they have to be proven in the store's own operation, not inherited from whoever sold the stack.

3. The cost that does not show up on the pricing page

When someone compares "native checkout versus Yampi", they usually compare only the card fee. The real calculation has at least six lines.

Shopify's additional fee for third-party providers

The official pricing page lists, plan by plan, an additional fee charged when the store uses a third-party payment provider instead of Shopify Payments (Shopify BR pricing). The amount changes by plan and Shopify revises the table, so the math has to be done with the page open that day and the store's invoice in hand. What does not change is the logic: leaving Shopify Payments can cost the store a slice of every sale, on top of the fee from the chosen gateway. Before signing up, ask the external checkout vendor, in writing, how their orders are counted in Shopify's billing for your store.

A second subscription and the vendor's fee

An external checkout is a second piece of software with its own billing model: a monthly plan, a percentage per order, or both. The official Yampi and Cartpanda pages are the only valid place for that number, and it needs to be read with the store's revenue alongside it. A percentage of sales looks small in a slow month and weighs heavily in a good one.

Losing Shop Pay

Shop Pay only exists inside the Shopify checkout (Shop Pay). With the redirect to the external checkout, a returning buyer who already has saved details loses the shortcut and types everything again. Baymard lists a long or complicated checkout among the reasons for abandonment (Baymard). Every extra field is another chance to give up.

Discounts, shipping and inventory in two places

The checkout is what calculates the total. If the checkout is external, coupons, shipping rules and promotions need to exist there too, or be kept in sync. A coupon created only in Shopify may simply not work in the external checkout, and the customer finds out at the moment of payment. The same goes for regional shipping rules and bundles: two sources of truth, two chances to drift apart.

Pixels and attribution

In the native checkout, pixels subscribe to checkout events through the Web Pixels API (Web Pixels API). In the external one, the purchase event happens on another domain, and Meta, Google Ads and GA4 need to be configured at the vendor, with deduplication between what the storefront sends and what the checkout sends. A wrong setup here does not break the sale, it breaks the campaign reporting, which is worse because nobody notices.

Split support

When an order does not show up, when inventory does not decrease or when a paid Pix does not confirm, the question becomes "whose problem is this": the theme, the integration app, the external checkout, the gateway or Shopify. Each support team looks only at its own part. The merchant becomes the integrator of their own system.

4. Native and external side by side

The criteria come from the official pages cited in the Source column. Fee and subscription amounts are left out on purpose: they change by plan and by date, and the decision has to be made with the official page open that day.

5. When an external checkout is justified

An external checkout is a tool for exceptions. These are the scenarios where it is worth opening the conversation, always with the store's own numbers:

The payment method you need does not exist in the native checkout

If Settings > Payments does not offer the method your audience requires, and no provider compatible with the native checkout solves it, the external checkout comes in as the solution. Here the criterion is binary: either the method exists in the native checkout or it does not.

The upsell funnel is the core of the model, and it is measured

A single-product operation sold through ads, where order bumps and post-purchase offers account for a meaningful share of revenue, can justify the switch. The condition is having the number: how much the upsell earns per order today, and how much it would need to earn to cover the fee, the subscription and the conversion lost without Shop Pay. Without that math, it is a gamble.

The checkout requirement needs Plus, and Plus does not fit

If the need is custom UI in the information, shipping or payment steps, the native checkout requires Shopify Plus (Checkout UI Extensions). Before going external, check whether a Function solves it through logic instead of the screen: hiding a method, changing the order, applying a conditional discount. A lot of "UI needs" are really business rules.

When it is not justified

• "Everyone uses it." That is not a requirement.
• "It needs Pix." Check the native checkout first.
• "Shopify's checkout is ugly." Appearance is adjusted under Settings > Checkout (checkout settings).
• "Cart recovery." First check what the Shopify admin and the apps that work on top of the native checkout already cover.

6. How to decide without guesswork

The diagnosis I run before any switch follows this order:

1. Payment inventory. Which methods the audience uses, and which ones the native checkout offers the store today.
2. Funnel inventory. Which upsell and recovery tools are running, and how much each one earns per order, sourced from the reports.
3. Full cost. The gateway fee, Shopify's additional fee, and the vendor's subscription and percentage, read from the official pages that day.
4. Dependency map. Coupons, shipping, bundles, pixels, ERP and anti-fraud: where each one lives today and where it would live afterwards.
5. Real order test. One purchase with Pix and one with a card, from the ad click to the order in the ERP, checking the purchase event in the ads manager.

If step 1 closes on the native checkout and step 2 shows no meaningful measured upsell, the answer is native. If the store is still on another platform, this diagnosis goes into the migration plan, together with the catalog, 301 redirects and DNS, as in the Loja Integrada migration checklist.

7. I already use an external checkout: can I go back?

Yes, and going back takes the same discipline as going out:

• Recreate in the native checkout the active coupons, shipping rules and promotions that currently exist only at the vendor.
• Activate and test the methods in Shopify Payments before turning off the checkout redirect.
• Redo the pixels for the native events and remove the vendor's, so purchases are not counted twice.
• Turn off the redirect during a low-traffic window, with a test purchase right after.
• Keep the history of orders and customers from the vendor before canceling the plan.

A checkout migration is smaller than a platform migration, but it breaks just the same when done blind: in the middle of a campaign and without a test order.

Frequently asked questions

Does Shopify have a transparent checkout in Brazil?

Yes. With Shopify Payments active, payment happens inside Shopify's own checkout, without redirecting the customer to an intermediary's page (Shopify Payments). The methods available to your store appear under Settings > Payments.

Yampi or Cartpanda: which one should I choose?

The question that comes first is whether you need an external checkout at all. If the diagnosis in section 6 says yes, compare the two by the requirement that motivated the switch (payment method, type of upsell, integration with your ERP) and by the full cost, read on the official Yampi and Cartpanda pages that day. Choose by requirement, not by a group recommendation.

Does an external checkout convert better than the native one?

There is no general answer published by an official source that supports this for every store. What exists is the certain cost of the switch (fees, subscription, Shop Pay out of the flow) against a gain that depends on your funnel. If someone promises higher conversion, ask for data from your category and the measurement method.

Will I lose SEO or orders when switching checkouts?

The checkout is not an indexed page, so SEO is not the risk. The risk is operational: a coupon that does not work, a duplicated or missing purchase event, an order that never reaches the ERP. That is why the switch, in either direction, ends with a real test order. If you are evaluating Shopify coming from another platform, the Tray vs Shopify comparison covers the checkout ceiling on the other side.

Conclusion

Shopify's native checkout, with Shopify Payments, is already a transparent checkout in Brazil and keeps sales, discounts, pixels and support in one place. Yampi and Cartpanda solve real cases, but they charge for it in fees, subscriptions, Shop Pay and complexity. That is why the order is native first and external by exception, with the requirement written down and the math done on the official pages. If you want to know whether your store fits the native checkout or whether an external one pays off in your case, send your current platform, plan, URL and the checkout you use today via oailton.dev/contato. If you have not created your Shopify store yet, talk to me before you do: the store starts as a development store, is built ready to go and is transferred to your name.