Short answer: Dynamics 365 cannot accept PIX or Boleto through its native card connectors. Neither method is a card, so no card gateway can process them. You either integrate a Brazilian PSP separately, or you connect Dynamics 365 once to a payment connector that already supports both. The connector route also covers local wallets, and it reconciles every transaction back into your ERP.

Brazil is where the “our gateway handles international” assumption breaks first. So it is worth understanding exactly why.

Why cards alone will not work in Brazil

PIX changed Brazilian payments quickly. It is an instant bank-transfer rail run by the central bank. It settles in seconds, it works around the clock, and Brazilian consumers adopted it at remarkable speed. Today a large share of Brazilian online purchases move through PIX rather than cards.

Boleto covers a different need. It is a printable or digital payment slip. The customer takes it to a bank, a lottery agent, or an app, and pays it — often in cash. Millions of Brazilians still buy this way, including plenty who hold no credit card at all.

Neither method touches the card networks. Therefore your existing acquirer cannot process them, however good your rates are. If you sell into Brazil with cards only, you are simply invisible to a large part of the market.

The methods that matter in Brazil

SensePass supports all six, alongside the other 112 payment methods in its network.

The usual alternative: a Brazilian PSP integration

Most Dynamics 365 merchants entering Brazil take one of two routes.

They integrate a local Brazilian PSP directly. That means a new contract, a new API, a new settlement file, and often a local entity requirement. Then they build the link into Dynamics 365 themselves and maintain it.

Or they wait. Frequently they launch with cards only, watch conversion disappoint, and revisit the question a year later.

Both routes have the same flaw. Whatever you build for Brazil does nothing for Mexico, Colombia, or Chile. Consequently each new market restarts the project.

How SensePass adds Brazilian methods to Dynamics 365

SensePass is a payment connector. It links the Dynamics 365 environment you already run to 112 payment methods and 50+ processors through one integration. PIX, Boleto and the Brazilian wallets are already built into it.

One integration, not one per country. You connect Dynamics 365 once. Then enabling PIX is a configuration step. So is enabling OXXO when you expand into Mexico, or PSE when you reach Colombia. Nothing changes inside Business Central, Finance & Operations, or Commerce.

No separate acquirer stack per market. SensePass stays processor-agnostic and already connects global and regional acquirers. Therefore you do not assemble a new payment stack for every country you enter.

Everything lands in one ledger. PIX confirmations and Boleto settlements flow back into Dynamics 365 automatically. As a result, your finance team reconciles one system rather than a separate Brazilian feed.

In-store too. If you sell physically in Brazil, tap-and-pay lets a customer tap their phone and pay with a local method at the register. No app download, and no dedicated terminal.

What PIX and Boleto change operationally

These two rails behave differently from cards, so plan for it.

PIX settles fast, which helps. Confirmation arrives in seconds, so you can release an order almost immediately. Compared with card authorisation and capture, the flow is simpler.

Boleto introduces a waiting period. The customer receives a slip and pays later — sometimes days later. Meanwhile your order sits unpaid. Therefore you need a clear rule for reserving stock, an expiry policy, and an order status that reflects “awaiting payment.” Our guide to cash and voucher payments covers that flow in detail.

Refunds differ by rail. A PIX refund returns funds to the payer’s bank account. A Boleto refund cannot simply reverse a cash payment at a lottery agent, so you refund through another route. Consequently your returns policy needs a Brazil-specific line.

Currency matters. You price and settle in Brazilian real. So use the transaction-date rate for the sale and the settlement-date rate for the payout, then post the difference to realised gain or loss.

Frequently asked questions

Can Dynamics 365 accept PIX? Not through native card connectors. PIX is a bank-transfer rail rather than a card, so it needs either a Brazilian PSP integration or a payment connector such as SensePass that already supports it.

What is Boleto, and why do I need it? Boleto is a payment slip that customers pay at banks, agents, or in apps, frequently in cash. It reaches Brazilian buyers who hold no card, so card-only checkouts lose those sales entirely.

Do I need a Brazilian entity to accept PIX? Requirements vary by provider and setup. However, a connector with existing regional acquirer relationships generally removes the need to assemble that stack yourself. Confirm the specifics for your business during scoping.

How quickly does PIX settle? Within seconds, and it operates continuously. Therefore you can confirm and release orders far faster than with several card flows.

Will these methods reconcile in Dynamics 365? Yes. Transactions post back into your ERP automatically, so you reconcile in one place rather than importing a separate Brazilian settlement feed.

Can I add other Latin American markets later? Yes, and that is the main argument for the connector route. See the Latin America country guide for what each market expects.

Does this work in physical stores? Yes. With tap-and-pay, customers tap their phone at the register and pay with a local method, with no app download required.

Sell in Brazil the way Brazilians pay

Cards will always be part of the mix. But in Brazil they are no longer the majority of it. One connector gives you PIX, Boleto and local wallets alongside everything else you already accept — and it reconciles the lot inside Dynamics 365.

Request a demo, or read the Dynamics 365 payments overview first.