close
    Contents

    Custom Checkout

    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 Worldline’s domain, not yours, while rendering them within iframes on your web page.

    Demo

    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 more examples of styled Custom Checkout. See a demo of Custom Checkout’s eventing. See a demo of a complete payment flow Custom Checkout.

    Custom Checkout vs Checkout

    Checkout is an alternative to building your own payment form with Custom Checkout.

    • Both solutions are PCI SAQ A compliant.
    • Checkout is a payment form - it creates sale and pre-auth transactions. Custom Checkout is a tokenizaton library - it returns a token that you use when creating transactions via the Payment API.
    • Checkout involves redirecting the user to a payment form on bambora.com. Custom Checkout embeds Worldline hosted input fields in your webpage.
    • Checkout is not brandable. Custom Checkout allows you to build a fully customized payment form - you retain as much control over UI/UX as you do with native DOM elements.

    Migration

    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.

    Browser support

    We support the latest versions of Chrome, Edge, Safari, and Firefox.