Riverty Buy-Now-Pay-Later Payment for OXID eShop 7
Riverty Buy-Now-Pay-Later for OXID eShop 7: invoice, direct debit, instalments and Pay in 3 via hosted checkout, multi-country, capture, void and refund in the admin.
Note on Riverty: This module is an independent integration and has no business or contractual relationship with Riverty. It was not commissioned, authorized or reviewed by Riverty. For questions or issues, please contact module support only (support@markus-michalski.net). Riverty itself takes no responsibility for and provides no support regarding this product. "Riverty" is a trademark of its respective owner.
This documentation always describes the latest published version.
Live Demo: Try this and other plugins live — no installation, no risk: demo.markus-michalski.net
Riverty Buy-Now-Pay-Later Payment for OXID eShop 7
Riverty Buy-Now-Pay-Later integration for OXID eShop 7: invoice, direct debit, instalments (Fixed Instalments) and Pay in 3 via Riverty's Hosted Checkout. The customer enters payment details on the Riverty page after the redirect, not in your shop. For OXID shop operators (CE/PE/EE) with a Riverty merchant contract selling in DE, AT, CH, NL, BE, NO, SE, DK or FI.
Riverty Buy-Now-Pay-Later is popular with customers, but the integration is complex: multi-country API keys, order lifecycle tracking, redirect flow, capture/void/refund logic. This module handles the entire integration. You manage configuration and order handling through the OXID admin, without writing any code.
Figure: Payment method selection at checkout
graph TD
A["Customer selects Riverty payment method"] --> B["Build authorize request"]
B --> C["RivertyClient: authorize()"]
C --> D{"Outcome?"}
D -->|Accepted| K["OXID order finalization proceeds"]
D -->|Pending| E["Redirect to Riverty Hosted Checkout"]
D -->|Rejected| F["Error message, back to payment selection"]
E --> G["Customer confirms at Riverty"]
G --> H["Return to return controller"]
H --> I["Verify signature or status lookup"]
I --> K
K --> L["Thank-you page with Riverty info box"]
Documentation
| Page | Content |
|---|---|
| Installation | Composer installation, activation, update |
| Configuration | API keys per country, fetching payment methods, settings, order management, API logs |
| Storefront | Payment methods at checkout, countries, instalment preview, thank-you page |
| Integration API and Console Commands | REST API for ERP/WMS, cron setup |
| Privacy | Which data goes to Riverty, what is stored locally |
| Troubleshooting | Common issues, FAQ |
| Technical | Checkout flow, order management flow, module structure, chain extending |
Features
| Feature | Description |
|---|---|
| Hosted Checkout | Payment process via Riverty redirect, payment details are not captured in your shop |
| Multi-Country | Separate API key pair (test/live) per country: DE, AT, CH, NL, BE, NO, SE, DK, FI |
| One-click payment method sync | A button creates the Riverty payment methods and assigns them to your configured countries |
| Order management | Capture, partial/full void, partial/full refund directly in the OXID admin |
| API logging | Every Riverty API call is logged and searchable in the admin |
| Integration API | External systems (ERP/WMS) can trigger capture/void/refund via REST (optional) |
| Sandbox mode | Switchable independently per country |
| Risk data enrichment | Optional existing-customer data for Riverty scoring |
| Instalment preview | Optional representative example per § 6a PAngV at checkout |
| Automatic data cleanup | A cron command clears out old logs and expired transactions |
Requirements
| Requirement | Version | Note |
|---|---|---|
| OXID eShop | 7.3+ | CE, PE or EE |
| PHP | 8.3+ | |
| Riverty | Merchant account | A contract with Riverty is required |
| License | Commercial | CE/PE: one installation; EE: one installation incl. all subshops |
License
Commercial license. CE/PE license: one installation. EE license: one installation including all subshops.
Support
Email: support@markus-michalski.net