We have an issue with the WHMCS checkout procedure. If a user fills in the checkout page and clicks submit and decides not to pay/payment fails, a user and and unpaid invoice are created. If that same user tries to pay at a later moment, the checkout page will not allow him to use the same email again , this confuses the user. If the user does use the email/pwd he did use on his first purchase attempt, he will go to the members area and find an UNPAID invoice, which also is confusing a lot of users as they think they do owe us money already. The work needed is described in detail below:
We use WHMCS as a subscription management system. Our checkout page is part of WHMCS and uses the flow set by the system when submitted: Create user account create order, service and invoice redirect user to payment gateway to complete the payment.
On our checkout page we use four main payment gateways:
Paypal: redirects the user to PayPal's website for payment completion, then sends a callback to WHMCS to confirm a payment.
Cardinity: a credit card method. A user enters his card information on the checkout page. The card info get sent to WHMCS for processing on submit. If a payment is successful, the user gets redirected to the Order Complete page. If not, then he is taken to a page to try again.
Paddle: The user gets redirected to Paddle's website for payment completion. Whether a payment is successful or not, the user stays on the Paddle payment page with no way back to our site. On successful payment, Paddle sends a callback (webhook) to WHMCS to confirm the payment.
Bitpay: the user gets sent to the Bitpay website for payment completion. On successful payment verification by the bitcoin network (which takes some time) , Bitpay sends a callback to our site to confirm the payment.
Currently, the issue we are having is that a user account is created whether a successful payment is made or not, leaving us a lot of abandoned user accounts that are pending payment.
We think that it is best to only create a user account in WHMCS after a successful payment is made with any of our payment gateways. We are looking for ideas and solutions on how to implement that without compromising on the functionality of WHMCS.
What we believe could work is that we create a standalone page in WHMCS that acts as a checkout page, where a user can enter his email and desired password, choose a subscription plan and a payment method, load the overlay (JS) versions of the payment methods we have on-screen, and have the user complete the payment on our checkout page without redirecting to another page, so that we can get the status of the payment immediately and choose whether to create an account or not.
However, we need to take into consideration that Bitpay cannot confirm payment immediately as the bitcoin network needs to verify it
apply with answer
Please try to describe your understanding of the problem
Please mention if you have done anything similar?
Please describe shortly what you think the best way to fix this is
thanks
About the recuiterMember since May 20, 2018 Johan Gunardi
from Maharashtra, India