Riverty Payment: Troubleshooting and FAQ
Troubleshooting Riverty for OXID eShop 7 - missing countries at checkout, signature errors, cron errors and the Integration API, plus FAQ.
Riverty Payment: Troubleshooting and FAQ
Live Demo: Try this and other plugins live — no installation, no risk: demo.markus-michalski.net
FAQ
Which payment methods does the module support?
Invoice, direct debit, instalments (Fixed Instalments) and Pay in 3 (Netherlands only). Which of them a customer sees additionally depends on your Riverty contract and the basket amount.
Does the module work with all OXID editions?
Yes, it requires OXID eShop 7.3 or newer (CE, PE or EE).
Do I need a separate API key for each country?
Yes. You enter a key pair (test and live) per country. A country without a matching key is not active.
Can I test in sandbox mode first?
Yes, sandbox mode can be switched independently per country. Live in one country and test in another is possible.
Why don't customers always see all payment methods at checkout?
Whenever the payment selection is opened, the module asks Riverty which payment methods are available for country and basket amount. Instalments, for example, only appear from a minimum amount. This is normal behaviour. Only country, currency, amounts and language are sent to Riverty, no customer data.
When is the payment captured?
Always manually: in the order's Riverty tab or via the Integration API. There is no automatic capture on shipping.
Troubleshooting (shop operator)
| Symptom | Check | Solution |
|---|---|---|
| Riverty payment methods are missing at checkout entirely | Was "Fetch & Sync Payment Methods" clicked after entering the keys? Is the payment method active and assigned to the country? | Click the button, check the "Configured Riverty Payment Methods" list |
| Country does not appear at checkout despite configuration | Does the stored API key match the sandbox switch (test key with sandbox on, live key with sandbox off)? | Add the missing key, then sync again |
| Instalments missing for a small basket | Is the amount below the minimum? | Normal behaviour, Riverty hides the payment method |
| Pay in 3 missing | Is the customer in the Netherlands and NL configured? | Pay in 3 exists for NL only |
| All Riverty payment methods vanish for a customer | Did Riverty reject the order in the risk check before? | Intended, applies to the current session only |
| Customer from NO/SE/DK/FI cannot proceed | Did they enter the identification number? | Required field at checkout, see Storefront |
| Signature error on return from Riverty | Does the country's API key match the one used at authorization? | Rule out a sandbox/live mix-up for that country |
| Payment rejected after return although successful at Riverty | Check the API logs for type lookup |
If the status lookup fails the module rejects to be safe |
| Order not marked as paid after "Capture Selected" | Which action was used? | That action sets neither paid date nor folder, see Configuration |
The API log under Riverty > API Logs is the first place to look. Use the "Type" filter and the order reference to narrow down individual payments.
Troubleshooting (developer / integration)
| Symptom | Check | Solution |
|---|---|---|
oe:riverty:cleanup aborts: setting not configured |
Are new settings present in the configuration after an update? | Run oe:module:apply-configuration or reactivate the module |
| Integration API returns 403 | Is "Enable external integration API" on? | Enable it in the admin and save |
| Integration API returns 503 | Has a secret been generated? | Click "Generate new secret" in the admin (shown only once) |
| Integration API returns 401 | Is the X-Riverty-Integration-Secret header correct? |
Check the secret or generate a new one |
| Integration API keeps returning 409 | Is an idempotency key reservation stuck? | Check the mmd_riverty_idempotency_keys table, delete the affected row if needed |
Integration API returns 400 with capture_number_required |
Was the item captured in several captures? | Send captureNumber in the refund request |