To facilitate PCI compliant credit card collections Fusebill provides a AJAX Transparent Redirect endpoint which you can use to securely capture customer's credit cards. If you are adding the first payment method on a customer, it will be set to the default payment method automatically.
This API action is authenticated with a separate Public API Key. If you do not have that key, please contact Fusebill Support. The Public Key can only be used to authenticate the Transparent Redirect action.
Fusebill leverages reCAPTCHA technology to ensure payment method data captured is provided by a human and to protect against bots and scripting.
We use Google reCAPTCHA V2 in order to accomplish this.
The basic workflow for how this is accomplished is as follows:
- Using Fusebill's public site key, the client is presented with a captcha widget.
- The user then verifies that they are human, starting with a check box. The user may be presented with additional verification steps such as an image recognition task.
- The captcha widget then verifies with Google that the user is human, and returns a response token.
- That response token is then sent to Fusebill with the payment method data for our system to validate and verify.
Sandbox and Production (payments.subscriptionplatform.com)
When using Fusebill Payments as your gateway processing account, some additional processing and data is required.
These are the ClientIP and a Risk token.
Additional information is available here.
Updated 10 months ago