RKR Refund Orders: Refunds on the payment gateway with a corrective invoice
Refund all or part of an order through the original payment gateway without leaving the back office: Stripe, PayPal, Redsys/Bizum, Paycomet, manually or via hook. Includes PDF invoice corrections, full audit trail, customer refund requests, statistics, and import/export functionality. Rekire module, tested in live stores.
Compatible with PrestaShop 1.7.8 to 9.2, with PHP 7.1 to 8.3.
Refunds
Getting a refund shouldn't be a three-screen process.
Refunding through the payment gateway, opening a separate invoice tool, and manually tracking who did what is time-consuming and prone to errors. RKR Refund Orders lets you refund the full or partial amount through the original payment gateway without leaving the order, providing a corrected invoice in PDF format and ensuring everything is properly recorded.
/ Refund from the order itself
You open the order and find the "Refund via Payment Gateway" panel. You see the amount charged, the amount already refunded, and the remaining balance that can be refunded. You select the lines and quantities, or enter a free amount, and you can include shipping costs. You choose the reason, add an internal note and a message for the customer, and click "Refund Now." The module detects the payment gateway used for the order; if any payment module requires a special rule, you define it.
Do you just want to register a return you already made elsewhere? "Just register" registers it without calling the payment gateway.
The gateways you already use
No duplicate charges
If the connection fails and you request a refund again, the module prevents it from being issued twice: it avoids this by order, amount, and connector. Failures are retried up to a limit you set, and you can require approval above a certain amount, so the payment gateway remains untouched until an authorized user releases the funds.
/ Corrective invoice ready, in PDF
Each refund generates its own credit note with its own unique numbering (prefix, first number, and leading zeros as you wish), including the issuer's name, legal notice, and footer in each language, printed in the language of the order. From the list, you can view, regenerate, send to the customer, or cancel it. Optionally, it also creates the native PrestaShop voucher, replenishes the stock, and changes the order status to "refunded" or "partially refunded."
/ That the customer requests the refund themselves
The store includes a "Request a Refund" page, accessible via a block in "My Account." Registered customers or guests can request a refund using their email address and order reference, which are verified against the order. You define the return window in days and the reasons for the return. From the back office, you can approve, reject with a response, or issue a refund with a single click. Smaller requests can also be automatically approved up to a specified amount, with a limit per customer every 30 days. If the payment gateway fails, the request is returned for manual review.
Everything is recorded
Import , export, and test risk-free
Export refunds, invoices, records, requests, and adjustments in CSV, JSON, or XML format. Import refunds and adjustments with a preview simulation that shows you the row and error report, and with automatic backups before each actual import. You can also install demo data to view all statuses and delete it with a single click without affecting your live data.
What worries us
To process refunds through the payment gateway, you need an active account and API credentials for each service (Stripe, PayPal, Redsys, Paycomet). The module uses cURL to communicate with them. Each gateway is a third-party service with its own terms and conditions. Always test with a small amount in test mode before using a live account.
Compatible with PrestaShop 1.7.8 to 9.2, with PHP 7.1 to 8.3
Developed and maintained by REKIRE
-
Referencerkrrefoundingorders
v1.4.4
Fixed
- Back office: the module's stylesheet and scripts were loaded on every screen, and its generic
.rkr-modal/.rkr-drawerrules (hidden until opened) left the dialogs of other Rekire modules invisible, such as the RKR Mail Editor editor on PrestaShop 9.0. They now load only on the module's own screens, its configuration page and the order and customer pages. - Every back office rule now only applies inside the module's own markup, the dialog classes are
.rro-modal/.rro-drawerand the animations are renamed, so nothing collides with another module even on a shared screen.
v1.4.3
Fixed
- Front office: the request page loaded neither its stylesheet nor its script (the asset paths carried a query string the core drops), and once the script loaded no request was ever saved (it disabled the submit button, so the form arrived without it).
- "Customers and guests" mode: a logged-in customer could not send a request, because the guest e-mail was required.
- "My account": the link uses the Hummingbird account menu (and the classic tile on Classic); the footer list gets a plain link.
- Order page panel: it vanished in debug mode and "Payments recorded" was always empty.
- Back office: "Refund via gateway", "Register only" and "New refund" did not open the refund window, and dismiss / confirm buttons did nothing (delegated click handlers).
- Filtering the refund, credit memo and log lists ended on the "Invalid token" page.
- Order states "Refunded" / "Partially refunded" are named in every language; status labels in the singular; request statuses, refund statuses and the policy error messages translated.
- Demo data: every demo credit memo had the same number, and some demo requests were 0.00.
- Credit memo preview: the shop logo did not load.
- Wide log tables run off the card at 1280 px; the customer's request table broke one word per line on a phone.
4 other products in the same category
Product Videos
Viewed products
Product Videos
También podría interesarte
Questions and answers
Nobody has asked anything about this product yet.