Available components
Load the script bundle
Add the following<script> tag to any page where you want to use Jupico web components. Load it once — all four components are included in the same bundle.
The URL above points to the sandbox environment. Update the hostname to the production URL when you go live.
Credit Card Form (<tokenization-form>)
The Credit Card Form collects and tokenizes card data without your servers ever handling the raw PAN. All field validation, security, and tokenization logic runs inside the component. When the customer submits, the component fires your submit-success callback with a one-time token.
Required properties
Methods
Code example
Bank Account / eCheck Form (<echeck-form>)
The Bank Account Form collects and tokenizes bank account details for ACH and eCheck payments. Like the credit card form, all validation, security, and tokenization are handled by Jupico. The component returns a one-time token through the submit-success callback.
Required properties
Optional properties
When setting this via a JavaScript property, use camelCase (
element.isRequired = true). When setting it as an HTML attribute, use lowercase (<echeck-form isrequired="true">).Code example
Full integration example
The example below shows all four components — credit card, eCheck, Apple Pay, and Google Pay — initialized from a single authorization session and appended to the same container.Best practices
Pass the same
sessions object to every component on a single payment page. Create one authorization session per page load and share it across the card form, eCheck form, Apple Pay, and Google Pay components. Do not create separate sessions per component.Framework compatibility (React, Vue, Angular): Jupico web components are standard custom elements and work in any framework. When using a JavaScript framework with dynamic data binding, use the programmatic HTML approach shown in the examples above — create the element with
document.createElement, set properties directly on the element reference, and append it to the DOM. This ensures that object properties like sessions and callback functions are bound correctly rather than serialized as attribute strings.
