Payment
Connect the payment reference and current status to the correct order.
Payments · Odoo integration
Make payment statuses useful in Odoo. Radorfa maps your process, configures the data exchange and tests it with your team.
First, we review your processes and systems. Then you receive a proposal with scope and costs.
Start with a feasibility check
We check API access, version and subscription before confirming the integration route.
ERP & CRMData, direction and frequency agreed for your environment.
Where the integration helps
A successful customer payment and a payout to your company are different events. We assess which Mollie information your Odoo order or administration needs. Existing Odoo payment modules are reviewed first; custom development follows only where your agreed process requires it.
We distinguish order payment from payout reconciliation in finance. Partial refunds and transaction fees need different handling from a successful payment. Together, we identify which steps your existing Odoo payment setup already covers.
We start with the task your colleagues need to complete. Which information is copied today, who checks it and which exceptions occur? Those answers determine the integration scope. We agree responsibilities with the people managing both applications before configuring access or transferring data.
Odoo and your application
Associate Mollie payment statuses with the relevant Odoo order or invoice, in line with your payment process.
Connect the payment reference and current status to the correct order.
Recognise full and partial refunds separately.
Align payouts, fees and accounting where required.
These are possible data flows. We agree the actual fields, direction and actions after checking both environments.
An example to discuss together
This is an illustrative scenario. We confirm the fields and actions available in your versions and subscriptions before making a proposal.
A payment has its own reference and status. We determine which Odoo order it belongs to.
We agree which confirmed payment status allows the next process step and how a refund becomes visible.
The later payout can contain multiple payments and fees. We separately define how your accounts team reconciles it.
We test a delayed status message, an expired payment, a partial refund and a notification received twice.
Bring your existing Odoo payment module, an anonymised payment reference and your payout reconciliation process.
Discuss this process →From requirements to everyday use
We discuss the required data flow with sales, warehouse or finance. For each piece of information, we define where it originates and which system leads.
We connect relevant Odoo modules such as Sales, CRM, Inventory and Invoicing. Test orders help us check fields, permissions, returns and duplicate messages.
You receive guidance on operation and error messages. We agree on monitoring, support, maintenance and checks following software updates.
We first review what your Odoo version and existing modules provide. Where needed, we use an existing connector, an integration platform or custom API development. Our advice considers your process, costs and ongoing management.
A delayed API, expired access or duplicate message should remain visible. We test retries, duplicate handling and notifications, and agree who follows up on exceptions.
A useful first conversation
Tell us which versions you use, which information should move and where your team loses time. We will discuss a concrete next step.
Frequently asked questions
No. We first review your existing Odoo payment module and required payment methods. Only missing process steps may require additional configuration or development.
A customer payment relates to a transaction; a payout to your business can combine multiple transactions and fees. We define how your accounts team checks those differences.
Costs depend on your systems, data flows, data quality, existing modules and required controls. We distinguish configuration, any licences and ongoing management. Share your applications and one concrete process so we can prepare a focused proposal.
Software updates can change fields, permissions or APIs. We document the configuration and agree how changes are tracked and retested. We also clarify the management and support process for incidents and functional changes.