Custom Checkout minimizes the scope of your PCI compliance - limiting it to SAQ A. It does this by isolating credit card data from your servers. It serves card input fields from Bambora’s domain, not yours, while rendering them within iframes on your web page.
Here is an example of a custom payment form styled with Bootstrap. Custom Checkout can be styled any way you choose. Try it out!
You can use using the test card number 4030 0000 1000 1234, with a security code 123 and any expiry date in the future.
See the Pen CustomCheckout-Bootstrap by na-bambora (@na-bambora) on CodePen.
See more examples of styled Custom Checkout. See a demo of Custom Checkout’s eventing. See a demo of a complete payment flow Custom Checkout.
Checkout is an alternative to building your own payment form with Custom Checkout.
Custom Checkout replaces our legacy Payfields/CheckoutFields, Payform and single use token scripts. These, along with direct posts to our Token API, are classified as SAQ A-EP solutions.
The token returned by Custom Checkout is identical to that returned by these other scripts. This means you can easily migrate to Custom Checkout by switching out the scripts on the client-side while leaving your server-side integration unchanged.
These are the browsers we actively test.