Does the module support all Riverty payment methods?
Yes: invoice, direct debit, instalments (Fixed Instalments), and Pay in 3 (currently only in the Netherlands, per Riverty's contract structure).
Does the module work with all OXID editions?
Yes, Community Edition, Professional Edition, and Enterprise Edition are all supported.
Do I need a separate Riverty contract for each country?
Yes — but the module itself manages any number of countries in parallel with no extra effort.
Can I test the module in sandbox mode first?
Yes, sandbox mode is switchable per country independently — running live in one country while testing in another is possible.
Do I need a developer to configure the module?
No. Installation and optional Integration API/cron setup are done once by a developer — the actual configuration (API keys, payment methods, settings) you do yourself in the admin afterwards.
Why don't customers always see all configured payment methods at checkout?
Riverty checks, on every call to the payment method selection, which payment methods are available for the current basket amount — instalments, for example, only appear above a minimum amount. This is expected behavior, not a bug. Only the basket amount is sent to Riverty for this, no customer data.
| Symptom | Check | Solution |
|---|---|---|
| Country doesn't appear at checkout despite configuration | Does the stored API key match the current sandbox toggle (test key when sandbox is on, live key when sandbox is off)? Have payment methods already been synced via "Fetch Payment Methods"? | Add the missing/correct key, then click "Fetch Payment Methods" again |
| Signature error on return from Riverty | Does the API key for the returning country match the one used at authorize time? | Rule out a sandbox/live mix-up for that country |
| Payment rejected on return, despite success at Riverty | Check the API logs for the lookup request type (see Configuration → API Logs) |
On an API error during status verification, the module rejects to be safe |
| Symptom | Check | Solution |
|---|---|---|
| Cron job fails with "setting not found" | Are the new settings present in the DB after the update? | Run oe:module:apply-configuration or reactivate the module |
| Integration API returns 503 | Has a secret been generated? | Customer generates one via the "Generate Secret" button in the admin (shown only once) |
| Integration API returns 409 persistently | Is an idempotency key reservation stuck? | Check the mmd_riverty_idempotency_keys table, delete the affected row if needed |