You are looking for
RO Payments can be used in two different ways with RSForm!Pro: StandaloneThis only uses the RO Payment fields Integrated with Payment Pro PackageThis uses the RO Payment button for use in the Payment Pro Package dropdown Creating a form using RO Payments standalone Using RO Payments in standalone mode requires at least the total field to...
The installation of RO Payments requires a few steps to be taken, by following this guide, it should be a fairly straightforward process. Requirements The following requirements must be met before you can start using RO Payments: An active contract with a payment provider A supported extension Installation Follow these steps to install...
RO Payments is a very versatile mediator between many Joomla extensions and a lot of payment providers. However payment providers keep popping up and there are so many payment providers already that we cannot support all of them. However there is the possibility of building your own payment provider into RO Payments.
RO Payments is the missing link between your site and the payment provider. Acting as a translator, it speaks the language of your extension and the language of the payment provider. As such providing a stable and trusted connection in the processing of payments on your site.
In every form there are a lot of placeholders available for various areas of customizing. The placeholders can now also be used in RO Payments to fully customize the user experience with the correct details. RO Payments allows you to create your own result messages to give a customer a tailored message based on the result of their payment.
RO Payments 5.0.0 This release has taken quite some time to see the light of day but today is the day that RO Payments 5 sees the light of day. Continuing on from JD iDEAL Gateway which has now been renamed to RO Payments. The majority of the improvements are under the hood. The code has been updated to meet the newest Joomla and PHP standards....
RO Payments 5.1.0 So we are continuing in improving RO Payments and this has resulted in a new release with a number of fixes and new features. Messages view The messages view has been revised and all columns are now sortable, so you can not only filter the messages but also sort them in your own desired order. Plugin names After the last...
Recurring payments is a feature that has been on the to-do list for some time. Most hosting providers do not even support recurring payments. This was until Mollie announced they are now supporting recurring payments. RO Payments now also supports recurring payments using Mollie.
Less than 2 weeks ago we came with the update of RO Payments 6.1.0 and we received some reports that users cannot open RO Payments. This is fixed in this RO Payments 6.2.0 release but we were also working on Joomla 4 support and this is ready for RO Payments core so we did not want to wait before releasing Joomla 4 support.
In RSForms! Pro it is possible to show multiple payment options on checkout combining the power of both RO Payments and RSForms! Pro Payment Package. By adding a new form field for every payment option you will create a list of payment options. The user can than select the desired payment option directly in the form.
In the last release of RO Payments a few things did not go as planned unfortunately, despite our own tests there were several issues identified that really needed some attention. In this release, RO Payments 6.0.2, we include the fixes for the issues that were brought to our attention.
A new major release of RO Payments which builds on the previous releases but in which we have cleared out some long standing issues and wishes. The configuration settings are now centralized in the places where they belong. A new way of managing placeholders makes it possible to be more flexible in using placeholders.
In most cases, the description that is going to be send to the payment provider can be customized in RO Payments. To customize the payment description, placeholders can be used. For example with RSForms you may want to add the name of a form field holding an invoice reference to the description.
Since the introduction of a new API at Mollie, a few new payment methods have been added. This means you need to check how the payment methods have been configured in RO Payments.
When a payment is not successful no email is send out via RSForms however there are cases where this may be useful. RO Payments has the option to send emails in case of payment failure in RSForms. This option can be sent per form so it does not affect any forms where this is not needed.
After the latest update of RSevents and RO payments, the RSevents no longer recognizes the RO payments option RSevents > Settings > Payments > Default payment method Either a bug of RSevents or RO payments.
On this page https://rolandd.com/products/ro-payments/installation the installation of RO Payments is described. However, there are no links under 'Extension' to information on how to install RO Payments as a payment plugin in HikaShop, although the text suggests that there should be (for that matter, that is the case for none of the extensions). Where do I dfind information on how to add RO Payments as a payment plugin in HikaShop please ? I have already setup a profile in RO Payments component.
Hello Elco, The process as you describe it won't work because RO Payments is not a payment provider. RO Payments cannot handle offline payments instead it connects to a payment provider such as Mollie. Here in lies also the solution i think. Mollie offers offline payments, also known as bank transfers. Instead of redirecting to iDEAL, you redirect to bank transfer. Users will receive an email with payment instructions. Once Mollie receives the payment it will inform your site that the status is paid. Now you have the same workflow as iDEAL although this can take up to 30 days depending on when a user pays. An offline payment isn't a successful payment until the user has paid. This document shows how you can setup different payment options on rsform. [url=https://rolandd.com/documentation/ro-payments/show-payment-options-in-rsforms-pro-form]https://rolandd.com/documentation/ro-payments/show-payment-options-in-rsforms-pro-form[/url] The bank transfer option must also be enabled on Mollie of course.
Hello Rakesh, The pre-sales is not meant for support of RO Payments, we only give support if you have an active subscription. RO Payments will show the payment status automatically when RSForms renders a directory view. There is nothing to configure in RO Payments.
Hello Roland, Mollie has accepted our account so we can now set the payment plugin, do i need both ROpayments and ROpayments for hikashop Or i just need the one for hikashop [b][EDIT] I tried to install ro payments for hikashop and got an error telling i had to install ro payments first so my first question is solved[/b] What is very interesting is what you told me about one plugin, for one payment method, because i can propose one payment method for certain countries and another one for another zone. Am I right? I may ask you other questions Patrick
Hello Patrick, [quote]I tried to install ro payments for hikashop and got an error telling i had to install ro payments first[/quote] Glad to see this check works :D [quote]What is very interesting is what you told me about one plugin, for one payment method, because i can propose one payment method for certain countries and another one for another zone. Am I right?[/quote] Correct. This is not an RO Payments feature but this comes from HikaShop. RO Payments really only does the payment when it gets triggered by HikaShop in your case.
Hello Frits, Some questions:[list=1] [*]How have you setup the payment options in RSForms? [*]Are you using RO Payments or the RSForm Payment Package? [*]Did you set them up like detailed in the [url=https://rolandd.com/documentation/ro-payments/show-payment-options-in-rsforms-pro-form]Show payment options in RSForms! Pro form[/url] document? [/list]
Hello Patrick, I am afraid you are looking at this the wrong way. What you see as [b]jdideal[/b] has nothing to do with the actual payment method used by the customer. The [b]jdideal[/b] is the internal name of RO Payments and HikaShop only stores the name of the plugin that was triggered, not the actual payment method. To see the actual payment method you can check that in RO Payments. If you want to know which HIkaShop payment is used, you need to look at the order_payment_id column and find that ID in the hikashop_payment table. As you can see in your second screenshot, all the payments are credit-card. As for what happened with this specific payment, I can't tell since the order has already been updated, so any information at that time is lost. The only place left to check is the Transactions log in RO Payments, this specifies which currency is passed on to RO Payments. You can find these logs on the Transaction page of RO Payments and then the last column.
Hello, The banktransfer option of Mollie takes you to Mollie because that is where the payment needs to be done. This is not just an option to show your bank details. Once the customer completes the banktransfer, Mollie will notify the website that the payment has completed (or not if the customer does not pay). This is the way all Mollie methods work. If you do not want to use Mollie for banktransfers you can still use the RSForms Pro Payment package in combination with RO Payments but your form fields must use the Payment package fields. See the documentation final paragraph at [url=https://rolandd.com/documentation/ro-payments/configure-rsforms-pro-with-ro-payments]Configure RSForms Pro with RO Payments[/url].
Hello, Which update do you mean? The RSForm! Pro 3 update or the RO Payments 6.5.0 update? The field has been called '(Payments) RO Payments' and this is only to be used with the RSForm! Pro payment package, as this field becomes a selection in the dropdown it renders. To use RSForm! Pro 3, you need to have RO Payments 6.5.0 as RSJoomla made some breaking changes for this not to work with older releases of RO Payments.
Hello Belto, The workings of a payment flow is always a bit tricky :) Let me try and explain how the flow works but first I have a question, when you say Ingenico terminal, do you mean a physical machine? RO Payments only works on websites. The flow is that the customer selects a product in your VirtueMart shop and goes to the checkout. In the checkout the customer can choose from different payment options. The customer selects a payment option and confirms the order. VirtueMart then creates the order and informs RO Payments of the chosen payment option. RO Payments then redirects the customer to Ingenico where the customer can pay. Once the customer has paid, Ingenico sends a message to RO Payments about the payment status and RO Payments informs VirtueMart. After that Ingenico sends the customer back to the website where the customer will see the result page. You can configure different payment methods in VirtueMart as you may know. Does that clarify the process more? Let me know if you have any further questions.
Hey Eric, [quote]If payments fail, the new user is registered anyway! [/quote] User registration is not done by RO Payments. [quote]At least the not-paid user should be deleted and the correct message should appear, IMHO.[/quote] This is not a task of RO Payments as it does not create the user either. This is going to need a custom plugin to react to the [url=https://rolandd.com/documentation/ro-payments/a-list-of-ro-payment-plugin-triggers]plugin triggers[/url] and take appropriate action or the plugin you use for creating the user should check the _STATUS field of a submission. This is out-of-scope for RO Payments. [quote]And no matter whether I switch the RSform messages on or off, the RO Payments message "payment failed" is never shown.[/quote] The failed message is shown if the response from Mollie is [b]fail[/b] or [b]failed[/b]. Is that also the status you get back? If you use the RSForm messages itself, there is no distinction based on payment status. This has to go through RO Payments. [quote]Am I doing something wrong?[/quote]I assume you have created the messages in RO Payments, if so that should be fine. There must be something with the status what is not triggering the message. To check what happens when you do not have a successful payment, post the screenshots of your RO Payments settings in RSForm, the transaction log and a screenshot of the messages you have. Are you not seeing any message when the status is cancelled?
Hello, Apologies for the missing documentation. I thought I had already written this. However the process is quite simple, you can follow these steps: [list=1] [*]Install RO Payments [*]Install the RO Payments - RSEventsPro plugin [*]Go to RSEventsPro [*]Click on Payments Integration in the right menu [*]You will get a list of payment methods and RO Payments/JD iDEAL is there as well [*]Click on [b]plg_rsepro_payment_jdideal_title[/b] [*]Here you can configure the settings. Most important here is to select the Profile you created in RO Payments. When a user completes the event registration, this profile will be used to complete the payment. [*]Save your settings [*]All done. [/list] Let me know if this helps.
Hello, RSForms itself has no option to show a message based on payment result. What you can do in the Form Properties -> RO Payments you can set the option [b]Show RSForm! Pro Thank you page[/b] to No as shown in screenshot. In that case RO Payments will show the message you have set in Messages in RO Payments. You can create a message for each payment result. Only downside is, you cannot use any of the RSForm Placeholders.
Hi Roland, Thanks for your reply. Before opening this ticket I to combine both the iDeal handling by RO Payments and the RSForm native offline payment. However in that setup not all products were added up in the grand total when selecting offline payment. You said: [quote]If you do not want to use Mollie for banktransfers you can still use the RSForms Pro Payment package in combination with RO Payments but your form fields must use the Payment package fields.[/quote] Does this mean that, in that case, all product fields and the grand total field should be from the RSForm payment package? Or, stating it differently: do I, in this case, use RSForm payment package fields for everything except for the iDeal payment option (from (payment) RO Payments)? I had the impression that this was not possible. Kind regards, Frits
Hi Tharuna, No worries, My client changed order status to 'pending' not knowing Ro Payments picks it ups and checks again if payment is received. Ro Payments is actually working super in this case ! Thanks for support anyway. Kind regards
Hello Steven, Not sure what you want me to do because as I have investigated this already and found out this is not an issue in the RO Payments code. [quote]only difference is we upgraded from JD Ideal to RO Payments on the problem site.[/quote] You did not update VirtueMart? The place where the error occurs doesn't even touch the RO Payments code. This must be something specific to this site because otherwise everybody would have this error. The only thing I could think of is to update VirtueMart to 3.8 on the test site, RO Payments to 6.0.2 and see how it goes. Check if it only happens with RO Payments on or also off. [quote]one thing I have noticed is in virtuemart it still says 'jd ideal" instead of ropayments?? [/quote]The name change is merely in the language files, not the code. What VirtueMart shows is the internal name. When you open the payment method you will see RO Payments in the plugin dropdown.
Hello Frits, [b]1. RO Payments mails for specific payment situations[/b] [quote]Form Properties > RO Payments > Configurable fields[/quote] This is not for use in the RO Payments emails, they are used to send to the payment provider. See the explanation at [url=https://rolandd.com/documentation/ro-payments/rsform-pro/rsform-pro-configurable-fields]RSForms Pro Configurable Fields[/url]. [quote]Is this not the correct way to set up the user email for these emails?[/quote]These emails should be used as a fallback mechanism actually. In a normal situation, not RO Payments but the extension itself should send out emails. RO Payments has no business logic of these extensions, that is why the emails of RO Payments are very limited. [quote]This issue might also account for the fact that I cannot send the Customer - Order Status Change email, if this takes its recipient from the same placeholder.[/quote]There is a discrepancy here I think. The system assumes the user is logged-in and takes the email from the users table. Are users logged-in for your form or they do not need to be logged-in? [quote]Also, I would prefer to send the Administrator - Payment Failed instead of the Payment Status mail.[/quote]This email is sent if the payment failed email is created, the profile the option to send an email on payment failure is set to Yes and the payment response failed. So an expired, cancelled, or any other valid status is not a payment failure. That should be why you are not receiving this email. This email is really more like an emergency email. [b]2. Confirmation email[/b] [quote] I tried to set the email address of the user as recipient[/quote]Ah, that will not work as it will only take the list of addresses entered into the field. This is really meant to just inform the form owner. Why not use the email feature of RSForm Pro that can be send out to the customer? [b]3. RSForm default emails[/b] [quote]If I leave these settings in RO Payments to no defer and I use the RSFom native settings instead, the behavior of the mails is as expected. So I managed to solve this one, but I thought that I should let you know anyway.[/quote] The defer option in RO Payments only works if you have disabled the RSForm Pro Payment Package as this will override whatever RO Payments does. Let me know if this helps or if I missed anything. Most important I guess is the question on the customer email.
Hello, Thank you for your interest. [list=1] [*]You cannot use any bank or any kind of gateway. It is impossible to support all banks and gateways in the world :) RO Payments supports [url=https://rolandd.com/products/ro-payments/features/payment-providers-support]a number of payment providers[/url], each payment provider offers a number of payment methods. All payment providers are for the Dutch market with the execption of Ingenico. Ingenico is a provider that can be used around the world and offers a large number of payment methods as well. [*]All payment providers we support use hosted checkout pages [/list] Let me know if you have any further questions.
Hello Rakesh, In that case please explain your issue further. Once the Artio payment plugin has been installed, all control is in Artio and only the payment is facilitated by RO Payments.