How to Set Up the Payment Gateway in Your Checkout
Learn how to integrate the payment gateway into your checkout, configure production credentials, and stop losing sales to setup errors.
What it means to set up the payment gateway in your checkout
Setting up the payment gateway in your checkout means connecting your store to the service that processes card and bank-slip payments, using production credentials and valid API keys. Without this step done right, the store gets traffic, gets clicks on the buy button, and doesn't approve a single transaction. The money shows up at the door and walks right back out.
This is the error that kills more operations on day one of selling than any other. You launch the campaign, burn budget, the pixel logs initiated checkouts, and not a single purchase comes through. Nine times out of ten it's not the creative. It's a badly configured gateway.
Why the gateway kills the sale before it even starts
Anyone who runs traffic knows it: the checkout is the last bottleneck before money comes in. If the gateway isn't plugged in, or it's plugged in the wrong way, the customer fills everything out, hits pay, and gets an error. Then they bail.
The classic mistake is building the whole store, setting up the product, dialing in the price, and forgetting to activate the gateway. The store looks ready. Visually everything's there. But the part that approves the payment simply never got connected.
In practice, here's what happens: you open your sales dashboard the next day, see 300 clicks on the campaign, 40 initiated checkouts, and zero approved. Panic sets in. You think it's the product. It's the gateway.
Test vs. production credentials: the difference that costs you
Every gateway gives you two environments: test and production. They exist for different reasons, and mixing them up is the number one setup failure.
The test environment lets you validate the flow without moving real money. You use a fake card, simulate the purchase, and see if the checkout responds. Useful for development. Useless for selling.
The production environment is the one that processes real payments. Real card, real money, real customer. If you launch the store with test credentials active, here's what happens: the transaction looks like it's going through, the system responds, but not a cent lands in your account. The customer sometimes even thinks they bought, and you see no sales on your statement.
Let me hammer this home because it's what kills operations: production credentials, never test. Before you turn the campaign on, check which environment is active in the checkout. That's the checkbox that decides whether you make money or burn budget for nothing.
How to generate the gateway's API keys
The gateway doesn't talk to the checkout by magic. It uses API keys, the credentials that authorize your store to process payments under that account.
The flow is simple:
- Go into your gateway's dashboard and find the integrations or API area
- Create a private API (some call it a secret key or server token)
- Copy the API key and the password (or secret key) that get generated
- Paste both fields into your checkout config, in the production environment
A lot of checkout platforms add a shortcut that takes you straight to the right credentials page inside the gateway. If you don't know where to find the key, look for that link before you go digging menu by menu.
Once the private API is created and the keys are copied, you go back to the checkout and finish the setup. Save it, and the gateway is actually plugged in.
Which payment methods should you turn on?
This is where you choose what shows up for the customer at payment time. The two most common in the Brazilian market:
Credit card. Instant approval, higher conversion, the method most of your traffic uses. Always on.
Bank slip (boleto). Lower conversion because the customer has to pay later, but it captures a slice of buyers who don't have a card or don't trust typing numbers online. In Nutra and nationalized international info-products, the boleto sometimes saves a sale the card would refuse.
The ideal is to keep both active. Every method you turn off is a chunk of audience that can't buy. If the gateway supports Pix, turn that on too, since it has instant approval and a low fee.
How to confirm the gateway is actually working
Don't trust the visuals. Test before you scale budget.
The safest way is to make a real test purchase, low value, using the production environment that's already active. You run an actual card, complete it, and check whether the transaction lands approved in the gateway's dashboard and on your statement. If it lands, it's working. If it errors out or sits pending for no reason, something's wrong with the key or the environment.
Anyone running an operation with several offers and multiple ad accounts feels this friction in another way: it's not just configuring one checkout, it's keeping dozens of Meta Ads campaigns pointed at the right place with no naming or destination errors. On the media side, standardizing campaign launches at scale (where platforms like DirectAds come in to eliminate human config errors across accounts) takes out a big chunk of the risk of spending budget sending traffic to a checkout that still doesn't close sales.
Once the test is approved, then you turn on the heavy campaign. Never the other way around.
Takeaways
- Check the gateway environment before anything else: production always, test never, or the store won't process real payments.
- Generate the private API, copy the key and password, and paste them into the checkout. Without a valid key, no transaction gets approved.
- Turn on card, bank slip, and Pix. Every method you leave off is an audience that can't buy.
- Run a low-value real test purchase before scaling. Only turn on budget after the sale lands approved on your statement.
Frequently asked questions
Why doesn't my store approve payments even with traffic coming in?
Most of the time it's the gateway in test mode or an invalid API key. The checkout responds but doesn't process real money. Check the production environment and revalidate the keys.
What's the difference between the API key and the gateway password?
The API key identifies your account and the password (or secret key) authorizes the transaction. Both fields need to be filled with production credentials for the payment to go through.
Do I need to turn on bank slip if the card already converts well?
The bank slip captures buyers without a card or who won't type numbers online. Conversion is lower, but it's a sale the card alone doesn't capture. Worth keeping on alongside Pix.
How do I test that the gateway works without taking a risk?
Make a low-value real purchase in the production environment and check whether it lands approved in the dashboard and on your statement. It's the only test that confirms the store actually closes sales.
