Changelog

What's New

OrionPay product and API release notes for merchants and integrators, newest firstRelease notes are published in English.

September 2026

Public pages fixed for small phones

Sep 18

The PIX QR code no longer gets cut off on narrow phones when the CPF dialog is open. Before, part of the code could be hidden and the QR would not scan; the code now shrinks to fit the screen. If a checkout would not scan on your phone in the last few days, try again.
The WhatsApp support button no longer covers the "Continuar" button on raffle, funding and campaign pages on mobile.
Buy and pay buttons across the public pages have a proper touch size again, and price labels no longer overflow in Spanish and French.
The product access page now wraps the access link instead of pushing it off the screen — the same page that asks you to save that link.
An invalid public address now shows a proper "page not found" screen with the Orion Pay header, footer and language switcher in all five languages, instead of a blank default page.
Alignment fixes on mobile and tablet: the language selector and menu sit at the right edge of the header; between phone and desktop widths the header no longer shows the same two buttons twice; the footer columns no longer overlap; Terms, Privacy, Fees, Docs and this changelog are aligned with the header; and the account-blocked page gained the language switcher.

Legal pages name the operating company again

Sep 18

The Terms, Privacy and Compliance pages, the site footer and the footer of every e-mail we send identify the company behind Orion Pay again: PROSPERITY DIGITAL LLC, registered in New Mexico, United States (Entity ID 0008048959), with its registered address and agent.
This identification had been dropped by mistake in an earlier clean-up, leaving the legal texts referring to a US-registered company without naming it. The rest of the legal texts did not change, and their "last updated" dates were not touched.
The same company data is now also published in a machine-readable format for search engines.

PIX withdrawals returned by the provider are now refunded automatically

Sep 17

When the PIX provider cannot deliver a withdrawal (for example, an invalid PIX key or a key that does not belong to the informed CPF/CNPJ), the DePix comes back to OrionPay and the full amount is returned to your balance automatically, as soon as the return is confirmed on the Liquid network. No more waiting for a manual review.
The reason the provider gave is now shown on the withdrawal, on the refund line and in the transaction details, together with the refund transaction id. Failed withdrawals now appear in your history by default, next to their refund.
When the PIX is rejected because of wrong recipient data (an invalid PIX key, or a key that does not belong to the informed CPF/CNPJ), a return fee of R$ 2,00 is charged as a separate line ("Taxa de devolução do saque #…") right after the refund, so your statement shows exactly what happened. The withdrawal screen now warns about it before you confirm. When the provider withholds nothing (the failure was not caused by the request), no fee is charged.
The refund line itself now states the reason ("Estorno do saque #… — Chave PIX inválida…"), so you do not have to open the details to see why the withdrawal came back.
You get an e-mail and an in-app notice when a withdrawal is returned. Check the PIX key and the recipient's document before trying again.
For integrations. The withdrawal.failed webhook now carries the provider's reason in error and, when applicable, providerRefundFee.

Create products, API keys and webhooks from the API

Sep 15

New endpoint POST /api/v1/personal/products: a single call creates a digital product, its product API key and, optionally, a signed webhook — and publishes the product so you can start charging with POST /api/v1/pix/generate right away. No more going through three dashboard screens before your integration can sell.
It works with your personal API key only; product keys are refused. The personal key itself is still created in the dashboard, and an activated Business account is required.
Supported types: online courses, photos, files, members area, Telegram channel, consulting and mentoring. For members-area and Telegram products you can send the access link in the same call.
Products with a fixed price come back with their checkout link (https://pay.orion.moe/p/…). New products are hidden from the marketplace by default.
Send an externalReference (your SKU or plan id) to make the call safe to retry: repeating it returns the product created the first time — with its key and webhook — instead of a duplicate. (If you disabled that key in the dashboard, the repeat returns no key; manage it there.)
For your security, the account owner gets an e-mail every time a product is created this way. Revoking the personal key does not revoke the product keys created with it — revoke those individually.
Product images, content (lessons, files), raffles, physical products, funding campaigns, and editing or deleting products stay in the dashboard.
Also available to AI assistants as the MCP tool personal_create_product. See the API docs.

Stricter webhook URL checks

Sep 15

Webhook URLs that point to local, private or internal networks are now refused when a webhook is created, or when its URL is edited, in the dashboard and in the API. Existing webhooks keep being delivered as before; if saving an edit fails, point the webhook to a public HTTPS address.

Webhook signature documentation corrected

Sep 15

For integrations. The OpenAPI spec (openapi.json) and llms-full.txt now describe webhook deliveries exactly as they are sent: a single X-Webhook-Signature header with the HMAC-SHA256 of the raw request body in lowercase hex (no sha256= prefix), and a JSON envelope with event, productId, productTitle, webhookName, an ISO-8601 timestamp and the event fields inside data.
Earlier versions of openapi.json described X-OrionPay-Signature, X-OrionPay-Event and X-OrionPay-Delivery headers that were never sent, and a flat payload. Deliveries themselves did not change — if you wrote your verification from that spec, check it against a real delivery and compute the HMAC over the raw body, not over re-serialized JSON.

August 2026

Your withdrawal receipt now shows what actually landed

Aug 25

The "Saque concluído" email now leads with the amount that reached your bank account, instead of the amount debited from your wallet. Before, the highlighted figure was the gross withdrawal — or the amount before the PIX provider's own fee — so it never matched the total you confirmed on screen.
The receipt now breaks the withdrawal down the same way the confirmation screen does: Valor solicitado, Taxa total and Valor recebido, and the three add up.
When the PIX provider reports the exact amount it paid out, the receipt uses that figure rather than the estimate shown at request time.

Withdrawal webhooks now report the net amount

Aug 25

Change for integrations. In the withdrawal.completed event, amount is now the amount the recipient actually received, and fee is the total fee charged (OrionPay plus the PIX provider). Previously amount carried the value handed to the payout provider, before that provider's fee, and fee covered only the OrionPay share — so both understated the cost of the withdrawal.
totalDeducted is unchanged: it is still the gross amount debited from the wallet. The three values now reconcile as totalDeducted − fee = amount.
If your reconciliation reads amount, review it before your next payout run. See the withdrawal.completed event in the API docs.

Get warned before a refund happens — and stop delivering

Aug 3

New webhook event payment.refund_pending: the PIX provider now warns us in advance when it is going to refund a payment it already received (risk or compliance reasons). It fires ahead of payment.refunded — about 2 hours earlier on average, and up to 3 days when the provider holds the amount first (the expected date comes in expectedRefundAt).
The payload carries rejectionReasons, the provider's own reason code — for example PAYER_MISMATCH when the paying account's document differs from the one the QR was locked to, or BLOCKED_USER. This is the provider's declared reason, not our inferred refundReasonDetail.
Buyer access is now revoked automatically. On sales with a DePix delay window, buyer access is granted at PIX confirmation, before settlement. If the provider then announces a refund, we cancel the purchase and revoke the access — the event reports accessRevoked: true so you can reverse fulfillment on your side too.
Sales that receive the warning before access is granted are no longer released at all: the deposit stays pending until the refund lands, instead of delivering the product against money that goes back to the payer.
See the payment.refund_pending event in the API docs for the full payload.

July 2026

Know why a PIX deposit was refunded — and re-engage the payer

Jul 24

The payment.refunded webhook now includes refundReasonDetail, a machine-readable reason for the refund: med_chargeback, cpf_mismatch, cnpj_mismatch, spam_like, user_blocked, or payer_refused.
Every refund now also carries payerEuid, a stable pseudonymous ID of the bank account that paid. Use it to correlate refunds from the same payer — for example, to issue a fresh QR code so the customer can pay again from the same account, or to block repeat offenders — without ever handling their personal identity.
On document-mismatch refunds (cpf_mismatch / cnpj_mismatch), the payload additionally includes the payer's name and tax ID so you can reconcile against the document typed at checkout. CPFs are always masked (***.999.999-**); company/PSP CNPJs are sent in full, as they are public registry data.
See the payment.refunded event in the API docs for full payload examples.

These release notes are now public

Jul 24

What's New is now published at pay.orion.moe/changelog, with the latest highlights also shown on the status page.

June 2026

Failed swaps are refunded automatically

Jun 27

If a currency swap fails before any funds leave your wallet, your balance is now returned to you automatically.
No support ticket or manual review needed for these pre-transfer failures — your money is available again right away.

New API guide for developers

Jun 27

A complete API integration guide is now available for developers and partners, with copy-paste code examples.
Covers generating PIX charges, selling products, payment-link checkout, and managing buyer access.
Documents secure, signed webhook notifications so your system can react automatically when a payment is received.

Smoother updates — no manual refresh

Jun 24

The web app now updates itself automatically after we release a new version, so you no longer need to hard-refresh the page.
If a page fails to load right after an update, it quietly reloads on its own and shows a brief "updating" indicator instead of an error screen.

Payer identification on PIX deposits

Jun 24

PIX deposits can now record the payer's tax ID (CPF/CNPJ), strengthening compliance and fraud protection.
When a deposit includes the payer's document, it is securely stored and masked in our systems.
Merchants can supply or collect the customer's CPF at checkout; payment links let customers enter it themselves.

WhatsApp support on every page

Jun 19

A floating WhatsApp button is now available across the site for quick access to OrionPay support.

More reliable PIX withdrawals

Jun 18

PIX withdrawals that briefly time out before any funds move are now retried automatically, so a temporary slowdown no longer fails the withdrawal.
This reduces cases where a withdrawal got stuck and had to be re-submitted by hand.
The retry only triggers when it's verified that no payment was sent, so there is no risk of paying twice.

Faster buyer access after payment

Jun 8

Buyers now get access to digital products as soon as their PIX payment is confirmed, instead of waiting for the full payment-clearing window.
The buyer's access link and the "access granted" notification to your store are sent right after confirmation.
Seller payouts continue to follow the normal settlement process, keeping payment protection in place.

Faster payment confirmation

Jun 5

PIX deposits that were briefly held for processing now have their payment confirmed and reflected in your dashboard noticeably sooner.
You and your customers get the "payment received" notification faster after the PIX is paid.
This speeds up when a payment shows as confirmed; any applicable holding period before funds become available is unchanged.

May 2026

Simpler plans: Basic and Business

May 22

Pricing is now two clear options: a free Basic plan and a paid Business plan.
Business unlocks merchant tools — product sales, invitations, and API & webhook access.
You can upgrade to Business at any time directly from your account.

Now available in 5 languages

May 19

The homepage, login and sign-up screens, and the Plans page are now available in Portuguese, English, Spanish, French, and Chinese.
Choose your preferred language to navigate account creation and pricing in the language you're most comfortable with.

Richer crypto balances on the dashboard

May 16

The crypto overview now shows each token's balance individually alongside the donut chart.
L-BTC and USDt balances are valued in Brazilian reais using live pricing from the Liquid Network.
A new selector lets you view your total balance denominated in DePIX, L-BTC, or USDt.

Orion Pay

Changelog

What's New

OrionPay product and API release notes for merchants and integrators, newest firstRelease notes are published in English.

September 2026

Public pages fixed for small phones

Sep 18

The PIX QR code no longer gets cut off on narrow phones when the CPF dialog is open. Before, part of the code could be hidden and the QR would not scan; the code now shrinks to fit the screen. If a checkout would not scan on your phone in the last few days, try again.
The WhatsApp support button no longer covers the "Continuar" button on raffle, funding and campaign pages on mobile.
Buy and pay buttons across the public pages have a proper touch size again, and price labels no longer overflow in Spanish and French.
The product access page now wraps the access link instead of pushing it off the screen — the same page that asks you to save that link.
An invalid public address now shows a proper "page not found" screen with the Orion Pay header, footer and language switcher in all five languages, instead of a blank default page.
Alignment fixes on mobile and tablet: the language selector and menu sit at the right edge of the header; between phone and desktop widths the header no longer shows the same two buttons twice; the footer columns no longer overlap; Terms, Privacy, Fees, Docs and this changelog are aligned with the header; and the account-blocked page gained the language switcher.

Legal pages name the operating company again

Sep 18

The Terms, Privacy and Compliance pages, the site footer and the footer of every e-mail we send identify the company behind Orion Pay again: PROSPERITY DIGITAL LLC, registered in New Mexico, United States (Entity ID 0008048959), with its registered address and agent.
This identification had been dropped by mistake in an earlier clean-up, leaving the legal texts referring to a US-registered company without naming it. The rest of the legal texts did not change, and their "last updated" dates were not touched.
The same company data is now also published in a machine-readable format for search engines.

PIX withdrawals returned by the provider are now refunded automatically

Sep 17

When the PIX provider cannot deliver a withdrawal (for example, an invalid PIX key or a key that does not belong to the informed CPF/CNPJ), the DePix comes back to OrionPay and the full amount is returned to your balance automatically, as soon as the return is confirmed on the Liquid network. No more waiting for a manual review.
The reason the provider gave is now shown on the withdrawal, on the refund line and in the transaction details, together with the refund transaction id. Failed withdrawals now appear in your history by default, next to their refund.
When the PIX is rejected because of wrong recipient data (an invalid PIX key, or a key that does not belong to the informed CPF/CNPJ), a return fee of R$ 2,00 is charged as a separate line ("Taxa de devolução do saque #…") right after the refund, so your statement shows exactly what happened. The withdrawal screen now warns about it before you confirm. When the provider withholds nothing (the failure was not caused by the request), no fee is charged.
The refund line itself now states the reason ("Estorno do saque #… — Chave PIX inválida…"), so you do not have to open the details to see why the withdrawal came back.
You get an e-mail and an in-app notice when a withdrawal is returned. Check the PIX key and the recipient's document before trying again.
For integrations. The withdrawal.failed webhook now carries the provider's reason in error and, when applicable, providerRefundFee.

Create products, API keys and webhooks from the API

Sep 15

New endpoint POST /api/v1/personal/products: a single call creates a digital product, its product API key and, optionally, a signed webhook — and publishes the product so you can start charging with POST /api/v1/pix/generate right away. No more going through three dashboard screens before your integration can sell.
It works with your personal API key only; product keys are refused. The personal key itself is still created in the dashboard, and an activated Business account is required.
Supported types: online courses, photos, files, members area, Telegram channel, consulting and mentoring. For members-area and Telegram products you can send the access link in the same call.
Products with a fixed price come back with their checkout link (https://pay.orion.moe/p/…). New products are hidden from the marketplace by default.
Send an externalReference (your SKU or plan id) to make the call safe to retry: repeating it returns the product created the first time — with its key and webhook — instead of a duplicate. (If you disabled that key in the dashboard, the repeat returns no key; manage it there.)
For your security, the account owner gets an e-mail every time a product is created this way. Revoking the personal key does not revoke the product keys created with it — revoke those individually.
Product images, content (lessons, files), raffles, physical products, funding campaigns, and editing or deleting products stay in the dashboard.
Also available to AI assistants as the MCP tool personal_create_product. See the API docs.

Stricter webhook URL checks

Sep 15

Webhook URLs that point to local, private or internal networks are now refused when a webhook is created, or when its URL is edited, in the dashboard and in the API. Existing webhooks keep being delivered as before; if saving an edit fails, point the webhook to a public HTTPS address.

Webhook signature documentation corrected

Sep 15

For integrations. The OpenAPI spec (openapi.json) and llms-full.txt now describe webhook deliveries exactly as they are sent: a single X-Webhook-Signature header with the HMAC-SHA256 of the raw request body in lowercase hex (no sha256= prefix), and a JSON envelope with event, productId, productTitle, webhookName, an ISO-8601 timestamp and the event fields inside data.
Earlier versions of openapi.json described X-OrionPay-Signature, X-OrionPay-Event and X-OrionPay-Delivery headers that were never sent, and a flat payload. Deliveries themselves did not change — if you wrote your verification from that spec, check it against a real delivery and compute the HMAC over the raw body, not over re-serialized JSON.

August 2026

Your withdrawal receipt now shows what actually landed

Aug 25

The "Saque concluído" email now leads with the amount that reached your bank account, instead of the amount debited from your wallet. Before, the highlighted figure was the gross withdrawal — or the amount before the PIX provider's own fee — so it never matched the total you confirmed on screen.
The receipt now breaks the withdrawal down the same way the confirmation screen does: Valor solicitado, Taxa total and Valor recebido, and the three add up.
When the PIX provider reports the exact amount it paid out, the receipt uses that figure rather than the estimate shown at request time.

Withdrawal webhooks now report the net amount

Aug 25

Change for integrations. In the withdrawal.completed event, amount is now the amount the recipient actually received, and fee is the total fee charged (OrionPay plus the PIX provider). Previously amount carried the value handed to the payout provider, before that provider's fee, and fee covered only the OrionPay share — so both understated the cost of the withdrawal.
totalDeducted is unchanged: it is still the gross amount debited from the wallet. The three values now reconcile as totalDeducted − fee = amount.
If your reconciliation reads amount, review it before your next payout run. See the withdrawal.completed event in the API docs.

Get warned before a refund happens — and stop delivering

Aug 3

New webhook event payment.refund_pending: the PIX provider now warns us in advance when it is going to refund a payment it already received (risk or compliance reasons). It fires ahead of payment.refunded — about 2 hours earlier on average, and up to 3 days when the provider holds the amount first (the expected date comes in expectedRefundAt).
The payload carries rejectionReasons, the provider's own reason code — for example PAYER_MISMATCH when the paying account's document differs from the one the QR was locked to, or BLOCKED_USER. This is the provider's declared reason, not our inferred refundReasonDetail.
Buyer access is now revoked automatically. On sales with a DePix delay window, buyer access is granted at PIX confirmation, before settlement. If the provider then announces a refund, we cancel the purchase and revoke the access — the event reports accessRevoked: true so you can reverse fulfillment on your side too.
Sales that receive the warning before access is granted are no longer released at all: the deposit stays pending until the refund lands, instead of delivering the product against money that goes back to the payer.
See the payment.refund_pending event in the API docs for the full payload.

July 2026

Know why a PIX deposit was refunded — and re-engage the payer

Jul 24

The payment.refunded webhook now includes refundReasonDetail, a machine-readable reason for the refund: med_chargeback, cpf_mismatch, cnpj_mismatch, spam_like, user_blocked, or payer_refused.
Every refund now also carries payerEuid, a stable pseudonymous ID of the bank account that paid. Use it to correlate refunds from the same payer — for example, to issue a fresh QR code so the customer can pay again from the same account, or to block repeat offenders — without ever handling their personal identity.
On document-mismatch refunds (cpf_mismatch / cnpj_mismatch), the payload additionally includes the payer's name and tax ID so you can reconcile against the document typed at checkout. CPFs are always masked (***.999.999-**); company/PSP CNPJs are sent in full, as they are public registry data.
See the payment.refunded event in the API docs for full payload examples.

These release notes are now public

Jul 24

What's New is now published at pay.orion.moe/changelog, with the latest highlights also shown on the status page.

June 2026

Failed swaps are refunded automatically

Jun 27

If a currency swap fails before any funds leave your wallet, your balance is now returned to you automatically.
No support ticket or manual review needed for these pre-transfer failures — your money is available again right away.

New API guide for developers

Jun 27

A complete API integration guide is now available for developers and partners, with copy-paste code examples.
Covers generating PIX charges, selling products, payment-link checkout, and managing buyer access.
Documents secure, signed webhook notifications so your system can react automatically when a payment is received.

Smoother updates — no manual refresh

Jun 24

The web app now updates itself automatically after we release a new version, so you no longer need to hard-refresh the page.
If a page fails to load right after an update, it quietly reloads on its own and shows a brief "updating" indicator instead of an error screen.

Payer identification on PIX deposits

Jun 24

PIX deposits can now record the payer's tax ID (CPF/CNPJ), strengthening compliance and fraud protection.
When a deposit includes the payer's document, it is securely stored and masked in our systems.
Merchants can supply or collect the customer's CPF at checkout; payment links let customers enter it themselves.

WhatsApp support on every page

Jun 19

A floating WhatsApp button is now available across the site for quick access to OrionPay support.

More reliable PIX withdrawals

Jun 18

PIX withdrawals that briefly time out before any funds move are now retried automatically, so a temporary slowdown no longer fails the withdrawal.
This reduces cases where a withdrawal got stuck and had to be re-submitted by hand.
The retry only triggers when it's verified that no payment was sent, so there is no risk of paying twice.

Faster buyer access after payment

Jun 8

Buyers now get access to digital products as soon as their PIX payment is confirmed, instead of waiting for the full payment-clearing window.
The buyer's access link and the "access granted" notification to your store are sent right after confirmation.
Seller payouts continue to follow the normal settlement process, keeping payment protection in place.

Faster payment confirmation

Jun 5

PIX deposits that were briefly held for processing now have their payment confirmed and reflected in your dashboard noticeably sooner.
You and your customers get the "payment received" notification faster after the PIX is paid.
This speeds up when a payment shows as confirmed; any applicable holding period before funds become available is unchanged.

May 2026

Simpler plans: Basic and Business

May 22

Pricing is now two clear options: a free Basic plan and a paid Business plan.
Business unlocks merchant tools — product sales, invitations, and API & webhook access.
You can upgrade to Business at any time directly from your account.

Now available in 5 languages

May 19

The homepage, login and sign-up screens, and the Plans page are now available in Portuguese, English, Spanish, French, and Chinese.
Choose your preferred language to navigate account creation and pricing in the language you're most comfortable with.

Richer crypto balances on the dashboard

May 16

The crypto overview now shows each token's balance individually alongside the donut chart.
L-BTC and USDt balances are valued in Brazilian reais using live pricing from the Liquid Network.
A new selector lets you view your total balance denominated in DePIX, L-BTC, or USDt.

What's New — Orion Pay