SDK Reference

Vaultera Switch’s SDK comes with a lot of features that give you complete control of your entire payment journey, from preloading to rendering and unmount. You can use the props to change the appearance, reorder payment methods and much more to suit your business needs.

The React SDK offers 2 integral elements for you to use:

Hooks
Components

The API for both the Hooks and Components are listed down below.

1. Hooks

`useSwitch()`

This hook gives you access to methods in Switch API, which you can call.

let vaultera_switch = useSwitch();

1. `vaultera_switch.confirmPayment(options)`

Use vaultera_switch.confirmPayment to confirm a PaymentIntent using data collected by the Payment Element. When called, vaultera_switch.confirmPayment will attempt to complete any required actions, such as authenticating your user by displaying a 3DS dialog or redirecting them to a bank authorization page. Your user will be redirected to the return_url you pass once the confirmation is complete.

options (Required)	Description
`elements (object)`	Required. The Elements instance that was used to create the Payment Element.
`confirmParams (object)`	Parameters that will be passed on to the Vaultera Switch API.
`redirect (string)`	Can be either ‘always’ or ‘if_required’ By default, `vaultera_switch.confirmPayment` will always redirect to your `return_url` after a successful confirmation. If you set redirect: “if_required”, then vaultera_switch.confirmPayment will only redirect if your user chooses a redirect-based payment method.

ConfirmParams object

confirmParams	Description
`return_url(string)`	Required. The url your customer will be directed to after they complete payment.
`shipping (object)`	The shipping details for the payment, if collected.
`payment_method_data (object)`	When you call `vaultera_switch.confirmPayment`, payment details are collected from the `HyperElement` and passed to the PaymentIntents confirm endpoint as the `payment_method_data` parameter. You can also include additional payment_method_data fields, which will be merged with the data collected from the `HyperElement`.

2. `vaultera_switch.elements(options)`

This method creates an Elements instance, which manages a group of elements.

options (Required)	Description
`font (array)`	An array of custom fonts, which elements created from the Elements object can use. Fonts can be specified as CssFontSource or CustomFontSource objects.
`locale (string)`	A locale to display placeholders and error strings in. Default is auto (Vaultera Switch detects the locale of the browser).
`clientSecret (string)`	Required Required to use with the Unified Checkout and Hyper Widgets.
`appearance (object)`	Match the design of your site with the appearance option. The layout of each Element stays consistent, but you can modify colors, fonts, borders, padding, and more.
`loader (variants)`	Can be either ‘auto’, ‘always’ or ‘never’ Display skeleton loader UI while waiting for Elements to be fully loaded, after they are mounted. Default is ‘auto’ (Vaultera Switch determines if a loader UI should be shown).

3.`vaultera_switch.confirmCardPayment(clientSecret,data?,options?)`

Use vaultera_switch.confirmCardPayment when the customer submits your payment form. When called, it will confirm the PaymentIntent with data you provide and carry out 3DS or other next actions if they are required. clientSecret is a required string.

data	Description
`payment_method(object)`	An object containing data to create a PaymentMethod with.
`shipping (object)`	The shipping details for the payment, if collected.
`return_url (string)`	Required. The url your customer will be directed to after they complete payment.

options	Description
`handleActions(boolean)`	An object containing data to create a PaymentMethod with.

payment_method example

  payment_method: {
    card: "card",
    billing_details: {
      name: "Jenny Rosen",
    },
  },

3. `vaultera_switch.retrievePaymentIntent(clientSecret)`

Retrieve a PaymentIntent using its client secret.

4. `vaultera_switch.paymentRequest(options)`

Use vaultera_switch.paymentRequest to create a PaymentRequest object. Creating a PaymentRequest requires that you configure it with an options object.

options (Required)	Description
`country (string)`	Required. The two-letter country code of your Vaultera Switch account (e.g., US).
`currency (string)`	Required. Three character currency code (e.g., USD).
`total (object)`	Required. A PaymentItem object. This PaymentItem is shown to the customer in the browser’s payment interface.
`displayItems (array)`	An array of PaymentItem objects. These objects are shown as line items in the browser’s payment interface. Note that the sum of the line item amounts does not need to add up to the total amount above.
`requestPayerName (boolean)`	recommended By default, the browser‘s payment interface only asks the customer for actual payment information. A customer name can be collected by setting this option to true. This collected name will appears in the PaymentResponse object.
`requestPayerEmail (boolean)`	Request the payer’s email-id.
`requestPayerPhone (boolean)`	request payer’s phone number
`requestShipping (boolean)`	request payer’s shipping information
`shippingOptions (array)`	An array of ShippingOption objects. The first shipping option listed appears in the browser payment interface as the default option.
`disableWallets (array)`	An array of wallet strings. Can be one or more of applePay, googlePay, link, and browserCard. Use this option to disable Apple Pay, Google Pay, Link, and/or browser-saved cards.

clientSecret is a required string.

5. `vaultera_switch.initiateUpdateIntent()`

Use vaultera_switch.initiateUpdateIntent() just before you start updating the payment intent on your end. It doesn’t require any input. When invoked, it signals the system to prepare for the update process and returns a confirmation message indicating that the update has been initiated.

6. `vaultera_switch.completeUpdateIntent(clientSecret)`

Use vaultera_switch.completeUpdateIntent(clientSecret) after you’ve completed the payment intent update process on your side. It takes the updated clientSecret as input and signals the system to complete the update flow. It returns a response with a confirmation message indicating the update has been processed.

useElements()

This hook gives you access to methods in Elements API, which you can call.

let elements = useElements();

1. `elements.getElement(type)`

This method retrieves a previously created Payment Element. Here the type is payment for Unified Checkout. elements.getElement(‘payment’) returns one of the following:

An instance of a Unified Checkout.
null, when no Unified Checkout has been created.\

2. elements.create(type, options?) This method creates an instance of an individual Element. It takes the type of Element to create as well as an options object. The type can be ‘payment’ for UnifiedCheckout. Options object

options (Required)	Description
`classes (object)`	Set custom class names on the container DOM element when the Hyper element is in a particular state.
`style`	Customize the appearance of this element using CSS properties passed in a Style object.
`hidePostalCode`	Hide the postal code field. Default is false. If you are already collecting a full billing address or postal code elsewhere, set this to true.
`iconStyle`	Appearance of the icon in the Element. Either solid or default.
`hideIcon`	Hides the icon in the Element. Default is false.
`disabled`	Applies a disabled state to the Element such that user input is not accepted. Default is false.

Classes object

classes	Description
`base`	The base class applied to the container. Defaults to HyperElement.
`complete`	The class name to apply when the Element is complete. Defaults to HyperElement—complete.
`focus`	The class name to apply when the Element is focused. Defaults to HyperElement—focus.
`invalid`	The class name to apply when the Element is invalid. Defaults to HyperElement—invalid.

3. element.update(options) Updates the options the Element was initialized with. Updates are merged into the existing configuration. If you collect certain information in a different part of your interface (e.g., ZIP or postal code), use element.update with the appropriate information. The styles of an Element can be dynamically changed using element.update. This method can be used to simulate CSS media queries that automatically adjust the size of elements when viewed on different devices

options	Description
`locale (string)`	A locale to display placeholders and error strings in. Default is auto (Vaultera Switch detects the locale of the browser).Setting the locale does not affect the behavior of postal code validation—a valid postal code for the billing country of the card is still required.
`appearance (object)`	Supported for the Unified CheckoutMatch the design of your site with the appearance option. The layout of each Element stays consistent, but you can modify colors, fonts, borders, padding, and more.
`clientSecret (string)`	Required to use with the Unified Checkout and the Hyper WidgetsThe client secret for a PaymentIntent

2. Components

`<VaulteraSwitchElements vaultera_switch options />`

This component wraps around the entire app and it consumes 2 parameters -

parameters	Description
`vaultera_switch (promise)`	This is the response that you get after calling the loadHyper() from the JS SDK. This will be the start point of your payment journey
`options (object)`	This follows the same API as vaultera_switch.elements()

`<UnifiedCheckout options onChange? onReady? onFocus? onBlur? onClick? />`

This component is the Unified Checkout itself which internally mounts the main iframe and subsequent iframes that are needed for the payment flow.

parameters	Description
`options (object)`	This has the same API as elements.create()
`onChange (function:event=>unit)`	This takes a callback function that gets triggered when any field is changed in the UnifiedCheckout
`onReady (function:event=>unit)`	This takes a callback function that gets triggered when UnifiedCheckout gets loaded.
`onFocus (function:event=>unit)`	This takes a callback function that gets triggered when a field is on focus in the UnifiedCheckout.
`onBlur (function:event=>unit)`	This takes a callback function that gets triggered when a field loses focus in the UnifiedCheckout.
`onClick (function:event=>unit)`	This takes a callback function that gets triggered when any clicks happen in the UnifiedCheckout.

`<CardWidget options onChange? onReady? onFocus? onBlur? onClick? />`

This component is the CardWidget, which is a 1 line payment method consisting of only card. This is a compact widget which fits anywhere in a webpage.

It follows the same API as Unified Checkout

`<CardNumberWidget options onChange? onReady? onFocus? onBlur? onClick? />`

This component loads up a small individual input field iframe which communicates with other iframes to collect card information and make API calls.

It follows the same API as Unified Checkout Note: You need to use it along with CardCVCWidget and CardExpiryWidget components, it cannot function as a standalone component.

`<CardCVCWidget options onChange? onReady? onFocus? onBlur? onClick? />`

This component loads up a small individual input field iframe which communicates with other iframes to collect card information and make API calls.

It follows the same API as Unified Checkout Note: You need to use it along with CardNumberWidget and CardExpiryWidget components, it cannot function as a standalone component.

`<CardExpiryWidget options onChange? onReady? onFocus? onBlur? onClick? />`

This component loads up a small individual input field iframe which communicates with other iframes to collect card information and make API calls.

It follows the same API as Unified Checkout Note: You need to use it along with CardCVCWidget and CardNumberWidget components, it cannot function as a standalone component.

Unified Checkout

The Unified Checkout provides developers a high level of customizability which enables them to shape their customer’s payment journey their own way. The snippet below explains all the options that are available to use for Unified Checkout.

  <UnifiedCheckout id="checkout" options={options}/>


  let options = {   // Options for creating the UnifiedCheckout.
    defaultValues: {  // Initial customer information can be passed to UnifiedCheckout that will be displayed / auto filled in the form. If not provided the form will render with empty fields.
        billingDetails: {    // To expedite the checkout process, you can enter the customer's billing information ahead of time, including their name, email, phone number, and address as needed for the payment method. By pre-populating the necessary fields with the customer's billing details, you can simplify and make the checkout process more efficient.
            name: string,
            email: string,
            phone: string,
            address: {
                line1: string,
                line2: string,
                city: string,
                state: string,
                country: string,
                postal_code: string,
            }
        }
    },
    layout: {  // [Type : String('tabs' | 'accordion') | Object] You can define the layout for the UnifiedCheckout in two ways. First, by simply passing a layout type such as 'accordion' or 'tabs', the UnifiedCheckout will be displayed using the default values associated with that layout. Alternatively, you can pass an object containing additional configuration parameters to further customize the layout of the UnifiedCheckout.
        type: string, // [Type : String('tabs' | 'accordion')] *REQUIRED*
        defaultCollapsed: boolean,  //This option allows you to choose whether the UnifiedCheckout should initially render in a collapsed state, with no payment method selected by default.
        radios: boolean, //For the accordion layout, the UnifiedCheckout renders each available Payment Method with a radio input next to its logo. The selected Payment Method is visually indicated by the corresponding radio button. Note that this property only applies to the accordion layout.
        spacedAccordionItems: boolean,  //When set to true, the available Payment Methods in the UnifiedCheckout are displayed as standalone buttons with spacing in between. Please note that this property is only relevant for the accordion layout.
    },
    business: {
        name: string, // You can enter your business details to be displayed in the UnifiedCheckout. If you don't provide this information, the UnifiedCheckout will retrieve the details from your Vaultera Switch account. It's worth noting that if you choose not to provide this information now, your business name may be used in the future.
    },
    customerPaymentMethods: // [Type : Array<customer_payment_methods>] The customer_payment_methods array contains the saved payment information of a customer that is provided during the creation of a payment intent. The UnifiedCheckout can then display this list of saved card/payment methods, making the checkout process faster and easier without any unnecessary hassle.
    paymentMethodOrder: array<string>, //[Possible Values: 'card' | 'affirm' | 'klarna' | 'afterpay_clearpay' | 'sofort' | 'giropay' | 'ideal' | 'eps'  | 'google_pay'  | 'apple_pay' | 'paypal'] By default, the UnifiedCheckout uses a dynamic ordering of payment methods that is optimized for each user. However, you can manually set the order in which payment methods are displayed by providing a list of payment method types.
    fields: {  //The UnifiedCheckout is designed to collect all the necessary information required to process a payment by default. However, for certain payment methods, the checkout may request information that you may have already collected from the user, such as name or email. If this is the case, you can prevent the UnifiedCheckout from collecting this data by using the fields option. If you disable the collection of a specific field using the fields option, you must manually pass that same data string `payment intent` creation or the payment will be rejected.
        billingDetails: { //[Type : String('never' | 'auto') | Object] To avoid collecting any billing details in the UnifiedCheckout, you can set the appropriate option to "never". Alternatively, you can choose to disable the collection of specific billing details by passing an object that specifies which fields you would like to disable collection for. By default, the setting for each field or object is "auto".
            name: string, //[Type : String('never' | 'auto')]
            email: string, //[Type : String('never' | 'auto')]
            phone: string, //[Type : String('never' | 'auto')]
            address: {  //[Type : String('never' | 'auto') | Object]
                line1: string, //[Type : String('never' | 'auto')]
                line2: string,  //[Type : String('never' | 'auto')]
                city: string, //[Type : String('never' | 'auto')]
                state: string, //[Type : String('never' | 'auto')]
                country: string, //[Type : String('never' | 'auto')]
                postal_code: string, //[Type : String('never' | 'auto')]
            }
        }
    },
    readOnly: boolean, //The readOnly option applies a read-only state to the UnifiedCheckout, preventing any changes to payment details. The default setting for this option is false. Enabling the readOnly option does not change the appearance of the UnifiedCheckout. If you want to customize the appearance of the checkout, you can use the Appearance object.
    wallets: {  //The UnifiedCheckout will, by default, display all payment methods associated with the underlying Payment Intent. This feature enables you to customize and display wallets based on your specific requirements.
        walletReturnUrl: string, //The walletReturnUrl is the return URL for all wallets. As the confirmPayment method handles other payment methods, wallets are displayed as a button and require a return URL to redirect back to your website for payment confirmation.
        applePay: string, //[Type : String('never' | 'auto')] To exclude a specific wallet from being displayed as a payment option, you can set its property to never. The default value of this property is auto.
        googlePay: string, //[Type : String('never' | 'auto')] To exclude a specific wallet from being displayed as a payment option, you can set its property to never. The default value of this property is auto.
        paypal: string, //[Type : String('never' | 'auto')] To exclude a specific wallet from being displayed as a payment option, you can set its property to never. The default value of this property is auto.
        style: {  //Style you wallet payment methods as per your requirements in terms of type, theme and height.
            type_: string, //[Possible Values: 'checkout' | 'pay' | 'buy' | 'installment' | 'pay' | 'default' | 'book' | 'donate'  | 'order'  | 'addmoney' | 'topup' | 'rent' | 'subscribe' | 'reload' | 'support' | 'tip' | 'contribute'] The type property in UnifiedCheckout allows customization of the button type, and the text on the button will be displayed accordingly. However, it's important to note that not all wallets support the same button type. If a type is provided that is not supported by a particular wallet, it will fallback to its default type.
            theme: string, //[Possible Values: 'dark' | 'light' | 'outline' ]
            height: int, //You can customize the height of the wallet button in the UnifiedCheckout using the height property. However, not all wallets support different height options. If you provide a height value that is outside the supported range of a particular wallet, it will fallback to either the maximum or minimum height value based on the value provided.
        }
    },
  }
  {
  "defaultValues": {
    "billingDetails": {
      "name": "string",
      "email": "string",
      "phone": "string",
      "address": {
        "line1": "string",
        "line2": "string",
        "city": "string",
        "state": "string",
        "country": "string",
        "postal_code": "string"
      }
    }
  },
  "layout": {
    "type": "string",
    "defaultCollapsed": "boolean",
    "radios": "boolean",
    "spacedAccordionItems": "boolean"
  },
  "business": {
    "name": "string"
  },
  "customerPaymentMethods": "array<customer_payment_methods>",
  "paymentMethodOrder": "array<string>",
  "fields": {
    "billingDetails": {
      "name": "string",
      "email": "string",
      "phone": "string",
      "address": {
        "line1": "string",
        "line2": "string",
        "city": "string",
        "state": "string",
        "country": "string",
        "postal_code": "string"
      }
    }
  },
  "readOnly": "boolean",
  "wallets": {
    "walletReturnUrl": "string",
    "applePay": "string",
    "googlePay": "string",
    "paypal": "string",
    "style": {
      "type": "string",
      "theme": "string",
      "height": "int"
    }
  }
  }

About Vaultera

Use Cases

Explore Vaultera

Checklist for Production

Essentials

1. Hooks

`useSwitch()`

1. `vaultera_switch.confirmPayment(options)`

2. `vaultera_switch.elements(options)`

3.`vaultera_switch.confirmCardPayment(clientSecret,data?,options?)`

3. `vaultera_switch.retrievePaymentIntent(clientSecret)`

4. `vaultera_switch.paymentRequest(options)`

5. `vaultera_switch.initiateUpdateIntent()`

6. `vaultera_switch.completeUpdateIntent(clientSecret)`

useElements()

1. `elements.getElement(type)`

2. Components

`<VaulteraSwitchElements vaultera_switch options />`

`<UnifiedCheckout options onChange? onReady? onFocus? onBlur? onClick? />`

`<CardWidget options onChange? onReady? onFocus? onBlur? onClick? />`

`<CardNumberWidget options onChange? onReady? onFocus? onBlur? onClick? />`

`<CardCVCWidget options onChange? onReady? onFocus? onBlur? onClick? />`

`<CardExpiryWidget options onChange? onReady? onFocus? onBlur? onClick? />`

Unified Checkout

​1. Hooks

​useSwitch()

​1. vaultera_switch.confirmPayment(options)

​2. vaultera_switch.elements(options)

​3.vaultera_switch.confirmCardPayment(clientSecret,data?,options?)

​3. vaultera_switch.retrievePaymentIntent(clientSecret)

​4. vaultera_switch.paymentRequest(options)

​5. vaultera_switch.initiateUpdateIntent()

​6. vaultera_switch.completeUpdateIntent(clientSecret)

​useElements()

​1. elements.getElement(type)

​2. Components

​<VaulteraSwitchElements vaultera_switch options />

​<UnifiedCheckout options onChange? onReady? onFocus? onBlur? onClick? />

​<CardWidget options onChange? onReady? onFocus? onBlur? onClick? />

​<CardNumberWidget options onChange? onReady? onFocus? onBlur? onClick? />

​<CardCVCWidget options onChange? onReady? onFocus? onBlur? onClick? />

​<CardExpiryWidget options onChange? onReady? onFocus? onBlur? onClick? />

​Unified Checkout

1. Hooks

`useSwitch()`

1. `vaultera_switch.confirmPayment(options)`

2. `vaultera_switch.elements(options)`

3.`vaultera_switch.confirmCardPayment(clientSecret,data?,options?)`

3. `vaultera_switch.retrievePaymentIntent(clientSecret)`

4. `vaultera_switch.paymentRequest(options)`

5. `vaultera_switch.initiateUpdateIntent()`

6. `vaultera_switch.completeUpdateIntent(clientSecret)`

useElements()

1. `elements.getElement(type)`

2. Components

`<VaulteraSwitchElements vaultera_switch options />`

`<UnifiedCheckout options onChange? onReady? onFocus? onBlur? onClick? />`

`<CardWidget options onChange? onReady? onFocus? onBlur? onClick? />`

`<CardNumberWidget options onChange? onReady? onFocus? onBlur? onClick? />`

`<CardCVCWidget options onChange? onReady? onFocus? onBlur? onClick? />`

`<CardExpiryWidget options onChange? onReady? onFocus? onBlur? onClick? />`

Unified Checkout