A published Odoo 19 module

What the listing names

The Odoo Apps listing identifies Blackstone Payment, technical name blackstone_payment, for Odoo 19.0. It describes website and store checkout, accounting invoice payments, remote collections, and recurring billing workflows. It lists Website, eCommerce, Discuss, and Invoicing as dependencies.

A module, not every Odoo integration

A payment provider module does not prove that every inventory, subscription, accounting, or custom app workflow is supported. Record the exact transactions your business needs before selecting a release.

Your edition, version, and hosting

Confirm installation options

The provider’s module page also describes version 19, a payment provider configuration, account credentials, refunds, and 3D Secure integration. Have the installer confirm the supported deployment method for your hosting and edition. A platform availability label is not proof that your subscription allows you to install modules from third parties.

Existing customizations

List modified checkout pages, fiscal rules, subscription changes, currencies, and other payment providers. Ask who will maintain the module after Odoo upgrades and how changes are tested.

Test the billing activity you use

Checkout and invoices

For an approved test sale, compare the order or invoice amount with the payment reference and accounting result. Include taxes, discounts, and any partial collection workflow your business requires. Do not close a balance solely because a payment request was sent.

Recurring payments and refunds

For repeat billing, confirm the actual schedule and what happens when a payment fails or a customer cancels. Test a refund and the records it changes. Published support for recurring workflows is a starting point for this review, not a guarantee about every subscription configuration.

Compare implementation and account costs

Get the complete proposal

Ask about module licensing, setup, hosting, maintenance, support, and gateway costs as well as processing fees. Establish who owns deployment, account activation, and reconciliation before agreeing to a transition date.