To facilitate PCI compliant credit card collections, Fusebill provides a basic transparent redirect endpoint which you can use to securely capture customers' 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 requires a separate public API key, and makes use of reCAPTCHA to protect against bots and scripting.
You can find your public API key under Settings > Integrations > Transparent Redirect
This version of transparent redirect uses a synchronous process wherein the end user is presented with a processing screen and is then taken to a success/fail URL depending on the result of the card validation. This makes it very straightforward to implement. If your web developers would rather handle the result asynchronously and in the client's browser, consider Fusebill's AJAX transparent redirect.


Fusebill Payments
When using Fusebill Payments as your gateway processing account, some additional processing and data is required.
These are the email
, clientIP
, and riskToken
Additional information for these fields is available here.
Updated 9 months ago