Update existing WHMCS tokenised payment gateway module -- 2
Budget: $10 – $30 USD
We have an existing tokenised payment gateway module. I've recently changed it from a merchant gateway module to a third party gateway.
The existing module also allows repeat capture payments to be taken as well. All of this works, but an extra tweak is needed that is beyond my knowledge.
The following needs to be completed:
- Add a new field to tblclients table, to store a secondary 'token' in WHMCS which will be generated by the payment gateway (which you would retrieve in the response, which is dealt with in the 'callback' code. This secondary token will need to be sent to the payment provider for any recurring payments (using WHMCS capture function), in addition to the primary token stored in the gatewayid field in tblclients.
- It seems that in the callback code, the developer opted to store the token into the gatewayid directly, rather than using the proper WHMCS built in function for this, so I would like this to be corrected. Ensure that token storage and repeat payments are working.
- Optimise/fix the code if you see any improvements that can be made - there may be some references to old 3d secure code that could be removed for instance.
I will provide you with the documentation for the payment gateway provider which includes coding examples.
Bidders should be familiar with WHMCS, and ideally have previous experience building payment/gateway modules in WHMCS.
Estimated time to complete is only a few hours.
The existing module also allows repeat capture payments to be taken as well. All of this works, but an extra tweak is needed that is beyond my knowledge.
The following needs to be completed:
- Add a new field to tblclients table, to store a secondary 'token' in WHMCS which will be generated by the payment gateway (which you would retrieve in the response, which is dealt with in the 'callback' code. This secondary token will need to be sent to the payment provider for any recurring payments (using WHMCS capture function), in addition to the primary token stored in the gatewayid field in tblclients.
- It seems that in the callback code, the developer opted to store the token into the gatewayid directly, rather than using the proper WHMCS built in function for this, so I would like this to be corrected. Ensure that token storage and repeat payments are working.
- Optimise/fix the code if you see any improvements that can be made - there may be some references to old 3d secure code that could be removed for instance.
I will provide you with the documentation for the payment gateway provider which includes coding examples.
Bidders should be familiar with WHMCS, and ideally have previous experience building payment/gateway modules in WHMCS.
Estimated time to complete is only a few hours.