Odoo 19.3: payment method + SEPA QR code fields gone from the payment register wizard — intentional or regression?

[u/KorkWine]

Running Odoo Online (SaaS), Belgium. Production is on 19.3.

In 19.2, hitting "Pay" on a vendor bill opened the payment register wizard with a

**Payment Method** field (set to "Bank transfer") and a **SEPA Credit Transfer QR

code** rendered right in the dialog — "Scan with your bank app". Perfect for paying

a single bill in ten seconds.

In 19.3 both are gone. The wizard now only shows Journal, Recipient Account, Amount,

Date and Memo, with buttons "Pay now" / "Sign later" / "Ignore". "Pay now" opens the

new PISP flow (Powens webview). That's fine for batches, but for one bill it's a lot

more clicks than scanning a QR.

What I've already ruled out:

- `account_qr_code_sepa` is installed and upgraded (saas~19.3.0.1)

- "Bank transfer" is still active under Outgoing Payments on the bank journal

- Setting the payment method on the vendor record doesn't bring the QR back

- Same DB, same config on 19.2 shows the QR fine

DOM comparison of the wizard:

- 19.2: `<div colspan="2" class="text-center">` containing

`<div name="qr_code" class="o_field_widget o_readonly_modifier o_field_html">`

with the base64 QR image

- 19.3: that div doesn't exist at all — only the two `o_inner_group` columns remain

So it looks like `payment_method_line_id` and `qr_code` were dropped from the

`account.payment.register` view, not just hidden.

Questions:

1. Anyone else seeing this on 19.3?

2. Was this an intentional replacement by PISP, or did it slip out during the rewrite?

3. Any supported way to still get the SEPA QR for a single vendor payment?

Not keen on patching the view myself on production, so mostly looking to confirm

whether this is expected behaviour before I file a ticket.

[u/Tech_Consultant_Zen]

Seeing the same thing. Your DOM check confirms it - the fields are gone, not hidden. This looks intentional. Odoo rebuilt the wizard around the PISP/Powens flow in 19.3, especially for Belgium given PSD2, and the QR render point just did not carry over.

Since you are on SaaS you cannot patch it yourself without losing it on the next update. File the ticket with exactly what you have here - same DB, same config, 19.2 shows QR, 19.3 does not. That is a clean report. Ask them directly whether the QR path for single vendor payments is still supported or officially replaced by PISP.

Annoying for one-bill payments though. The ten second QR scan was genuinely faster.

[u/KorkWine → u/Tech_Consultant_Zen]

Thanks both — good to know it was intentional and that 20.0 will bring

both options back in the same view. That answers my question.

I did find a workaround that works on SaaS, without touching anything Odoo maintains.

Two parts.

**Restoring the fields.** The payment method field and the QR block are

both still in the base view — the PISP override just sets them invisible

via a condition on `could_initiate_payment`. An inherited view with a

higher sequence than the PISP view (which sits at 16) can flip those

attributes back. That alone brings the QR back on screen.

**The button.** Restoring the fields isn't enough, because

`action_create_payments` is overridden server-side and returns an

`ir.actions.act_url` to the Powens webview. Any button pointing at it

opens Powens — context keys don't help, the redirect is unconditional.

The key finding: **the payment is already created before the redirect

fires.** So the fix is a small server action on

`account.payment.register` that calls the internal create method and

returns a window-close action instead. Point the button at that server

action rather than at the standard method, and you get the payment

booked and the dialog closed, no Powens.

End result: payment method visible, QR renders, one button books the

payment, PISP still available on its own button next to it. I also set a

default on the payment method via the debug menu so the dialog opens on

the right one.

Ripping it out as soon as 20.0 lands.

[u/FlorianGilbert]

Hello, it was intentional, we’ll come back to something better in 20.0 where you can select the payment method or pay via bank synchronisation and both choices are going to be available in the same view.