Checkout Web integration

This guide helps you get started with the Checkout SDK on web browsers.

Prerequisite

A Mangopay ClientId and API key (get a Sandbox API key for free)
A User and their associated Wallet to complete the pay-in
A card to register or payment method setup (see Testing - Payment methods for testing information)

Supported browsers: Chrome 117, Firefox 118, Safari 16, or higher

Installation

You can install the Mangopay Checkout SDK using npm or yarn.

Install with npm:

$ npm install --save @mangopay/checkout-sdk

Install with yarn:

$ yarn add @mangopay/checkout-sdk

Install via CDN

If you are using script tags to load files, include the Mangopay SDK script in your HTML:

1 <script src="https://checkout.mangopay.com/sdk/checkout-sdk.min.js"></script>

Warning – Load script from Mangopay Checkout domain

To maintain PCI compliance, the script must be loaded directly from the Mangopay Checkout domain:

http://checkout.mangopay.com

The script must not be bundled or hosted on other domains. You must reference it directly from our domain.

Content Security Policy (CSP)

Caution - Allow policies if using CSP

If your web page is using the Content-Security-Policy response header, you need to allow the policies below.

Policy	URLs
script-src	*.google.com
connect-src	api.mangopay.com api.sandbox.mangopay.com *.payline.com

script-src

*.google.com

connect-src

api.mangopay.com

api.sandbox.mangopay.com

*.payline.com

Initialization

Initialize the SDK and specify the configuration options.

Example - Initialization

1 import { CheckoutSdk } from '@mangopay/checkout-sdk';
2 
3 const mangopaySdk = await CheckoutSdk.loadCheckoutSdk(elementOrSelector, options);

Initialization parameters

Property	Type	Description
`elementOrSelector`	HTMLElement \| String REQUIRED	The container element or the selector of the container element.
`options`	Object REQUIRED	The options of the Checkout SDK configuration.

options

The child parameters of the options object parameter:

Property	Type	Description
`clientId`	String REQUIRED	The unique identifier associated with the Mangopay API key, giving access to the Mangopay API.
`environment`	String	The Mangopay environment. Allowed values: SANDBOX, PRODUCTION Default values: SANDBOX
`profilingMerchantId`	String REQUIRED	The unique identifier associated with your fraud protection package. Contact Mangopay to obtain this value.
`amount`	String REQUIRED	Information about the debited funds. The currency (ISO_4217 format) and value (expressed in minor units) of the debited funds.
`paymentMethods`	Array REQUIRED	The payment methods presented to the user. Array of objects detailing the `type` and configuration `options` for specific payment methods. Each payment method includes configuration options tailored to its specific requirements.
`respectPaymentMethodsOrder`	Boolean	Controls how payment methods are ordered and which one is initially active. When `true`, the SDK renders methods in the order provided by `paymentMethods` and the first item in that array becomes the initial selection. When `false` (default), `card` is rendered first and used as the initial selection; other methods are rendered in an order determined by the SDK. Default value: `false`
`branding`	Object	The custom branding of the payment page (see Customization section below).
`locale`	String \| Object	The language for the payment page. Specify one of the built-in languages (`en`, `fr`) or send an object with custom messages (see Customization section below).
`tenantId`	String	The Mangopay tenant being used by the platform. Platforms that have contracted with Mangopay’s UK entity must set the value to `UK`. Allowed values: `EU`, `UK` Default value: `EU`
`clientToken`	String	A token used to authenticate and enable specific SDK features. Today, only PayPal One-Click requires a `clientToken` (PayPal without One-Click and other payment methods do not require it). Obtain the `clientToken` from your server before initializing the SDK - see the PayPal One-Click section for details.

Configuration

Configure the MangopayCheckout parameters and delegates.

Example - Vanilla JS

HTML

1 <body>
2     <div id="checkoutForm">
3         <div id="container"></div>
4     </div>
5     <script src="/index.js"></script>
6 </body>

JavaScript

1 window.addEventListener('load', async () => {
2     const mangopaySdk = await CheckoutSdk.loadCheckoutSdk('#container', options);
3     if (!mangopaySdk) {
4         throw new Error('Failed to load MangopayCheckoutSdk');
5     }
6 
7     mangopaySdk.on('error', (event: CustomEvent<ErrorEventDetails>) => console.error(event.detail));
8 
9     mangopaySdk.on('tokenizationComplete', (event: CustomEvent<TokenizationCompleteEventDetails>) => {
10         // handle tokenization complete
11     });
12 
13     mangopaySdk.on('paymentComplete', (event: CustomEvent<PaymentCompleteEventDetails>) => {
14         // handle payment complete
15     });
16 });

Example - ReactJS

JavaScript

1 import { MangopayCheckout } from '@mangopay/checkout-sdk-react';
2 
3 const CheckoutComponent = () => {
4 
5   const sdkRef = useRef(null);
6 
7   const onTokenizationComplete = () => {
8       /* Handle Card/GooglePay/ApplePay token here
9              e.g charge customer card using CardId
10       */
11   };
12 
13   const onPaymentComplete = () => {
14       /* Handle Card/PayPal payment complete */
15   };
16 
17   const onCancel = () => {
18       /* Handle cancellation of payment  */
19   };
20 
21   return (
22     <MangopayCheckout
23       ref={sdkRef}
24       options={options}
25       disabled={disabled}
26       onError={onError}
27       onLoaded={onLoaded}
28       onChange={onChange}
29       onTokenizationComplete={onTokenizationComplete}
30       onPaymentComplete={onPaymentComplete}
31       onCancel={onCancel}
32     />
33   )
34 }

MangopayCheckout parameters

Property	Type	Description
`ref`	React.RefObject<MangopayCheckoutForwardedRef>	React reference object: `import { MangopayCheckoutForwardedRef } from '@mangopay/checkout-sdk-react';`
`onPaymentComplete`	Function(event)	Triggered when the transaction is completed, whatever the outcome (whether successful or failed).
`options`	Object	Checkout SDK configuration options
`disabled`	Boolean	Applies a disabled state to the Checkout component such that user input is not accepted.
`onError`	Function(event)	Triggered when an internal SDK error has occurred.
`onLoaded`	Function(event)	Triggered when the Checkout SDK is loaded.
`onChange`	Function(event)	Triggered when data exposed by the Checkout SDK is changed.
`onTokenizationComplete`	Function(event)	Triggered when: A card tokenization is completed and a `CardId` is returned. The user authorizes a Google Pay or Apple Pay payment.
`onPaymentComplete`	Function(event)	Triggered when the transaction is completed, whatever the outcome (whether successful or failed).
`onCancel`	Function()	Triggered when the payment process is canceled by the user. This can occur when the 3D Secure authentication window or PayPal, Google Pay, or Apple Pay popup is closed before completion.

Updating options

After the SDK has been initialized you can update the options without needing to fully reinitialize again by using the updateOptions method. Make sure you pass a complete updated options object as specified in the Configuration section.

1 import { CheckoutSdk } from '@mangopay/checkout-sdk';
2 const mangopaySdk = await CheckoutSdk.loadCheckoutSdk('#container', options);
3 // update options
4 mangopaySdk.updateOptions({...options, amount: {...options.amount, value: updatedValue});

Handling redirection

Warning – Use Mangopay Checkout domain as return URL

When making the pay-in request from your backend, use the Mangopay Checkout URL as the SecureModeReturnURL or ReturnURL (depending on the payment method):

http://checkout.mangopay.com

The user must be returned to this URL after redirection.

Some payment methods (card, Google Pay, PayPal) require or may require the user to be redirected to authorize or complete a transaction.

The Checkout SDK allows you to manage the entire payment flow seamlessly while retaining control over transaction logic in your backend. Once a payment method is selected and payment details are provided, use the options.onCreatePayment function to request the transaction from your backend.

Subsequently, and when necessary for the transaction type, the Checkout SDK seamlessly manages additional redirect actions for 3DS authorization or otherwise validating the payment.

To manage transaction redirects effectively with the SDK:

Define onCreatePayment

In your paymentMethods configurations, define an options.onCreatePayment attribute as a function.

Within your function:

Request a transaction from your server and subsequently, Mangopay.
Return the unaltered transaction response object to the SDK.

The SDK:

Redirects the user to the payment authentication page when necessary.
Manages payment provider redirects back to the SDK.
Triggers the onPaymentComplete event with the ID and status of the transaction.
Confirms the redirect result on your server by invoking the corresponding GET API of the transaction.
Presents the payment result to the user.

1 paymentMethods: [
2     {
3         type: 'card | paypal | googlepay',
4         onCreatePayment: function (event) {
5             // 1. implement server-side call to request a transaction.
6             // 2. return the card transaction object.
7         }
8     }
9 ]

Configuring card payments

To configure the card payment method, specify card as the type of the paymentMethods object. For the options, use the following configuration parameters.

options

Property	Type	Description
`options.supportedCardBrands`	Array REQUIRED	The card brands supported. Allowed values: VISA, MASTERCARD, AMEX, MAESTRO, CB
`options.onCreateCardRegistration`	Function REQUIRED	Use this attribute to request and return a Card Registration.
`options.onCreatePayment`	Function REQUIRED	To handle 3DS redirects for card payments, use this attribute to request and return a pay-in.
`options.enableSaveCard`	Boolean	If set to `true`, a Save Card checkbox will appear in the UI. When checked, `SaveCard: true` will be returned in the `CreatePaymentData` object, and you can forward this flag to your backend for further handling (read more about managing saved cards).
`options.savedCards`	Array of `SavedCard`	A list of cards previously saved by the user. If provided, a button will appear within the card number input field that opens a dropdown of saved cards to select from.
`options.onDeactivateSavedCard`	Function	A callback that is triggered when the user chooses to deactivate a saved card. Receives an object containing `{ cardId: string }`. You can use this ID to inform your backend which card should be deactivated.

Card configuration example

TypeScript

1 export interface CreatePaymentData {
2   Id: string;
3   Tag: string;
4   CreationDate: string;
5   UserId: string;
6   CardId: string;
7   CardType: string;
8   Currency: string;
9   PreferredCardNetwork?: 'VISA' | 'MASTERCARD' | 'CB' | 'MAESTRO';
10   ProfilingAttemptReference: string;
11   SaveCard: boolean;
12 }
13 
14 export interface SavedCard {
15     Id: string;
16     ExpirationDate: string;
17     CreationDate: number;
18     Alias: string;
19     Tag?: string;
20     CardProvider: CardBrand;
21     CardType: string;
22     Country: string;
23     Product: string;
24     BankCode: string;
25     Active: boolean;
26     Currency: string;
27     Validity: string;
28     UserId: string;
29     CardHolderName: string;
30     Fingerprint: string;
31     PreferredCardNetwork?: CardBrand;
32 }
33 
34 const options = {
35     clientId: 'MANGOPAY_CLIENT_ID',
36     environment: 'SANDBOX | PRODUCTION',
37     amount: {
38         value: 1000,
39         currency: "EUR"
40     },
41     paymentMethods: [
42         {
43             type: 'card',
44             enableSaveCard: true,  // show the “Save Card” checkbox
45             savedCards: [
46                 {
47                     Id: '12345',
48                     ExpirationDate: '1026',
49                     CreationDate: 1692817000,
50                     Alias: 'XXXX XXXX XXXX 1234',
51                     CardProvider: 'MASTERCARD',
52                     CardType: 'CB_VISA_MASTERCARD',
53                     Country: 'FR',
54                     Product: 'Debit',
55                     BankCode: '01234',
56                     Active: true,
57                     Currency: 'EUR',
58                     Validity: 'VALID',
59                     UserId: '67890',
60                     CardHolderName: 'John Doe',
61                     Fingerprint: 'fing3rpr1nt'
62                 }
63             ],
64             onDeactivateSavedCard: function({ cardId }) {
65                 // 1. Call your server to remove card and deactivate in Mangopay API
66             },
67             onCreateCardRegistration: function (cardType: 'CB_VISA_MASTERCARD' | 'AMEX' | 'MAESTRO') {
68                 // 1. Implement server-side call to create a card registration.
69                 // 2. Return the card registration.
70             },
71             onCreatePayment: function (event: CreatePaymentData) {
72                 // 1. Implement server-side call to request a card transaction.
73                 // 2. Return the card transaction object.
74                 // 3. The SDK handles 3DS redirect for you.
75             }
76         }
77     ]
78 };
79 const mangopaySdk = await CheckoutSdk.loadCheckoutSdk(elementOrSelector, options);

Card tokenization

In the options for the card payment method, create a function to handle creation of Card Registration event handler in the paymentMethods object:

Your onCreateCardRegistration function calls your server, and passes it the card brand of the user.
Your server makes a request to Create a Card Registration.
In response, your server receives a Card Registration object.
In your onCreateCardRegistration function, return the unmodified Card Registration object to the SDK.
The SDK tokenizes the card and updates the Card Registration object to create the CardId which is used for payment.

TypeScript

1 // Vanilla JS
2 mangopaySdk.on('tokenizationComplete', (event: CustomEvent<TokenizationCompleteEventDetails>) => {
3     // handle tokenization complete
4 });
5 
6 mangopaySdk.on('paymentComplete', (event: CustomEvent<PaymentCompleteEventDetails>) => {
7     // handle payment complete
8 });
9 
10 // React.js
11 const onTokenizationComplete = () => {
12     // handle tokenization complete
13 };
14 
15 const onPaymentComplete = () => {
16     // handle payment complete
17 };
18 
19 <MangopayCheckout
20     ref={sdkRef}
21     options={options}
22     onTokenizationComplete={onTokenizationComplete}
23     onPaymentComplete={onPaymentComplete}
24 />

tokenizationComplete output

REST

1 {
2   "Id": "cardreg_m_01HQ0J6GB3JFZ1NC5EGCJBE4PB",
3   "Tag": null,
4   "CreationDate": 1708342329,
5   "UserId": "user_m_01HP6ZG0XXZ89V34GRZEY9HQCE",
6   "AccessKey": "1X0m87dmM2LiwFgxPLBJ",
7   "PreregistrationData": "YkgVxL1yNY4ZOfKtqEew_Zj34Eg4_H3r-UyvrLWB_MHYF1OqkWAtDMwDMZ0pSZfliRF4hvSrtJCvT7-9XAi0Xsj7Q1OS-vT4lpHzEztZoLs",
8   "RegistrationData": "data=iN_eoipU7i2AEuTss7wuoPRZYTuNVHlTvhc4dEXHczhSWquUg8N2vrbXU91rCDepo0Fw6rcqxRBK8KMWk8xhHGOBEuIr9_d-Xo64K6cr5w-lY2yXbTUOs7e-S6CpTShm",
9   "CardId": "card_m_01HQ0J6H02QXH3HATEYW0FMJKP",
10   "CardType": "CB_VISA_MASTERCARD",
11   "CardRegistrationURL": "https://pci.sandbox.mangopay.com/api/mangopay/vault/tokenize/eyJjbGllbnQiOiJjbGllbnRJZCIsInRva2VuIjoidW5xaXVlVG9rZW4ifQ==",
12   "ResultCode": "000000",
13   "ResultMessage": "Success",
14   "Currency": "EUR",
15   "Status": "VALIDATED",
16   "ProfilingAttemptReference": "25e5c450-7f00-4805-af04-4330e4dc0cee"
17 }

Requesting card pay-ins

You can use a registered card (CardId) for requests with the following API objects:

The Card Validation object, to validate a card without debit
The Direct Card PayIn object, for one-shot card payments
The Recurring PayIn Registration object, for recurring card payments
The Preauthorization object, for 7-day preauthorized card payments
The Deposit Preauthorization object, for 30-day preauthorized card payments

In your requests:

Ensure that the SecureModeReturnURL parameter is set to https://checkout.mangopay.com
Submit the PreferredCardNetwork value if it was received by onCreatePayment

Managing saved cards

The Checkout SDK can allow the user to save their card for a future payment.

Enable saving cards

To enable saving cards, set enableSaveCard to true to present a Save card checkbox on the user interface.

Deactivate if card not saved

If the user doesn’t check the box, then the CreatePaymentData object returns SaveCard : false. In this case, you must systematically call PUT Deactivate or edit a Card to deactivate it in the Mangopay API.

If saved, store tokenized card in your system

If the user checks the box, the SaveCard flag is set to true and passed to your onCreatePayment handler. You can then store the card object in your system.

Re-use saved cards

To present the user’s saved cards in the next payment session, send an array of card objects in the savedCards array in the payment method configuration.

If sent, then a dropdown appears in the interface in the card number input field. When a saved card is selected, the SDK uses it for the payment process.

Deactivate card if user removes it

In the dropdown, there is an option for the user to remove a saved card. In this case, the onDeactivateSavedCard is triggered and you must:

Remove the card in your system
Call PUT Deactivate or edit a Card to deactivate it in the Mangopay API

Caution - Deactivate card systematically unless user saves it

Under no circumstances should card information be kept without the end user’s approval.

If CreatePaymentData returns SaveCard : false, indicating the user doesn’t wish to save it, then you must call PUT Deactivate or edit a Card to deactivate it in the Mangopay API.

The same is true if the onDeactivateSavedCard is triggered, indicating that the user wishes to remove the card.

Diagram - Saved cards

The following diagram shows the flow of managing saved cards:

Saved card example

TypeScript

1 const options = {
2   amount: {
3     value: 1000,
4     currency: 'EUR'
5   },
6   paymentMethods: [
7     {
8       type: 'card',
9       enableSaveCard: true, // display the "Save Card" checkbox
10       savedCards: [
11         {
12           Id: '12345',
13           Alias: '497010XXXXXX8183',
14           ExpirationDate: '1026',
15           CardProvider: 'MASTERCARD',
16           Active: true,
17           UserId: '67890',
18           Validity: 'VALID',
19           CardType: 'CB_VISA_MASTERCARD',
20           Country: 'FRA',
21           Product: 'I',
22           BankCode: 'unknown',
23           Currency: 'EUR',
24           Tag: null,
25           CreationDate: 1744280826,
26           Fingerprint: '48d63bbcfc2c47fcbc19df35e47b2f8d',
27           CardHolderName: 'John Doe'
28         }
29       ],
30       onDeactivateSavedCard: function({ cardId }) {
31         // 1. Call your server to remove card and deactivate in Mangopay API
32       },
33       onCreatePayment: function (event) {
34         // 1. Check if event.SaveCard === true
35         // 2. Deactivate if false
36       }
37     }
38   ]
39 };
40 
41 // Vanilla JS
42 const mangopaySdk = await CheckoutSdk.loadCheckoutSdk('#container', options);
43 
44 // React.js
45 <MangopayCheckout ref={sdkRef} options={options} />

Configuring Apple Pay

Note - Apple Pay integration required

Offering Apple Pay requires additional setup by the platform, including certification and integration. For more information, see the Apple Pay guide.

Caution - Apple Pay on the Web availability

Apple Pay on the Web, using the JavaScript Checkout SDK, is only available on Mac and iOS devices. Apple Pay on the Web also requires additional certification.

To configure the Apple Pay payment method, specify apple_pay as the type of the paymentMethods object. For the options, use the following configuration parameters.

Apple Pay configuration options

Property	Type	Description
`paymentRequest`	Object REQUIRED	The specifications of the payment request.
`onCreatePayment`	Function REQUIRED	Function called after the user has successfully authenticated a card for payment from the Apple Pay sheet. Use this attribute to implement backend creation of the Apple Pay PayIn from your server. After creating the pay-in, return the pay-in object to the SDK.

paymentRequest

Property	Type	Description
`countryCode`	String REQUIRED	The platform’s two-letter ISO 3166 country code.
`currencyCode`	String REQUIRED	The three-letter ISO 4217 code (EUR, GBP, etc) of a supported currency (depends on feature, contract, and activation settings).
`merchantCapabilities`	Array REQUIRED	Information about the card types and authentication protocols you support (see Apple Pay documentation).
`supportedNetworks`	Array REQUIRED	The card networks supported by Mangopay Allowed values: `visa`, `masterCard`
`total`	Object REQUIRED	The line item total for the payment (see Apple Pay documentation).
`merchantIdentifier`	String REQUIRED	Your platform’s Apple Pay Merchant ID.
`merchantName`	String REQUIRED	The name of your platform.
`onValidateMerchant`	Function REQUIRED	Use this attribute to request and return a ApplePay session. Function called when the SDK receives an onvalidatemerchant merchant event from the Apple Pay sheet. The assigned function should implement backend creation of the merchant session object from your server. After creating the session object, return the session object to the SDK.
`requiredBillingContactFields`	Array REQUIRED	The billing information to fulfill the order (see Apple Pay documentation).

Requesting the merchant session from your server

Displaying the Apple Pay payment sheet using the Mangopay Checkout SDK works as follows:

You generate the merchant session from your server
The SDK’s onValidateMerchant function calls your server and passes it the static hostname apple-pay-gateway.apple.com as the validation URL. In the China region, use cn-apple-pay-gateway.apple.com.
Your server uses the validation URL to request a session from the Apple Pay server, as described in Requesting an Apple Pay Payment Session.
In the response, your server receives an opaque merchant session object: MerchantSession.
You pass the merchant session object to the completeMerchantValidation method of the SDK (see Apple Pay documentation for more information on this method).

1 //Define ApplePay Merchant session delegate
2 const validateApplePayMerchant = (validationURL: string): Promise<ApplePayMerchantSession> => {
3 	return fetch(
4     'https://backend-api-url/get-apple-pay-session',
5     method: 'POST',
6     body: JSON.stringify({
7       validationURL,
8       merchantIdentifier: 'merchant.com.example.mystore',
9 	    displayName: 'MyStore',
10 	    initiative: 'web',
11 	    initiativeContext: 'mystore.example.com'
12     })
13   );
14 };

Requesting Apple Pay pay-in

To request the payment, use the Create an Apple Pay PayIn endpoint and include the Apple Pay PaymentData.

Set up payment delegate – Assign a delegate function to the onCreatePayment attribute in your Apple Pay options.
Handle payment authorization – After the user successfully authorizes a card for payment through the Apple Pay sheet, the SDK will call your onCreatePayment function and pass the PaymentData to it.
Create pay-in – Implement the backend creation of the Apple Pay PayIn on your server using the PaymentData provided.
Return pay-in object – After creating the pay-in, return the pay-in object to the SDK.

1 interface CreateApplePayPaymentData {
2   PaymentData: {
3     transactionId: string;
4     network: string;
5     tokenData: string;
6   };
7   ProfilingAttemptReference?: string;
8 }
9 
10 //Define ApplePay PayIn delegate
11 const handleCreateApplePayPayIn = (data: CreateApplePayPaymentData): Promise<CreateApplePayPayInResult> => {
12 	return fetch(
13     'https://backend-api-url/create-applepay-payin',
14     method: 'POST',
15     body: JSON.stringify(data)
16   );
17 };

Apple Pay configuration example

TypeScript

1 const options = {
2   clientId: 'MANGOPAY_CLIENT_ID',
3 	environment: 'SANDBOX | PRODUCTION',
4 	paymentMethods: [
5 		{
6       type: 'apple_pay',
7       options: {
8         paymentRequest: {
9           countryCode: 'IE',
10           currencyCode: 'EUR',
11           merchantCapabilities: ['supports3DS'],
12           supportedNetworks: ['visa', 'masterCard'],
13           total: {
14             label: 'Demo (Card is not charged)',
15             type: 'final',
16             amount: '20.00',
17           },
18           merchantIdentifier: 'merchant.com.example.mystore',
19           merchantName: 'MyStore',
20           onValidateMerchant: validateApplePayMerchant,
21           requiredBillingContactFields: ['email']
22         },
23         onCreatePayment: handleCreateApplePayPayIn
24       },
25     }
26 	]
27 };
28 
29 // Vanilla JS
30 const mangopaySdk = await CheckoutSdk.loadCheckoutSdk(elementOrSelector, options);
31 
32 // React.js
33 <MangopayCheckout ref={sdkRef} options={options} />

Configuring Google Pay

Note - Google Pay setup required

Offering Google Pay requires additional setup by the platform. For more information, see the Google Pay guide.

Caution - Add Mangopay Checkout to your Google Console

You need to add checkout.mangopay.com along with your domain to the authorized list in the Google Business Console to view the Google Pay payment popup.

This allows the Checkout SDK to ensure the Google Pay experience is presented appropriately to your users. Not following this guidance may impact your payment acceptance on Google Pay.

To configure the Google Pay payment method, specify google_pay as the type of the paymentMethods object. For the options, use the following configuration parameters.

Google Pay configuration options

Property	Type	Description
`merchantInfo.merchantId`	String REQUIRED	Your Google Pay Business ID, which you can find in Google Pay & Wallet Console.
`merchantInfo.merchantName`	String REQUIRED	Your Google Pay Business Name, which you can find in Google Pay & Wallet Console.
`gateway`	String REQUIRED	The orchestration used: in this case, whenthen. Allowed values: whenthen
`gatewayMerchantId`	String REQUIRED	Your Mangopay `ClientId`.
`cardParameters.allowedAuthMethods`	Array REQUIRED	The supported authentication methods: PAN_ONLY, meaning the card is registered in the user’s Google account and requires additional authentication; CRYPTOGRAM_3DS, meaning the card is enrolled in the customer’s Google Wallet and authentication is handled by Google, with no 3DS redirection and no liability for the platform. Allowed values: PAN_ONLY, CRYPTOGRAM_3DS
`cardParameters.allowedCardNetworks`	Array REQUIRED	The card networks supported by Mangopay. Allowed values: VISA, MASTERCARD
`transactionInfo`	Object REQUIRED	Information about the transaction and its authorization, such as whether the user agrees to the transaction, the total price and price status. For more information on this object parameter, see the Google Pay documentation.
`onCreatePayment`	Function REQUIRED	Function called after the user has successfully authorized a card for payment from the Google Pay sheet. The assigned function should implement backend creation of the Google Pay PayIn from your server. After creating the pay-in, return the pay-in object to the SDK.
`button.buttonColor`	String	The color of the button. Default value: default Allowed values: default – A Google-selected default value (currently black but it may change over time). black – A black button suitable for use on white or light backgrounds. white – A white button suitable for use on colorful backgrounds.
`button.buttonType`	String	The type of the button, determining the text to display. Default value: buy Allowed values: book – The “Book with Google Pay” payment button. buy – The “Buy with Google Pay” payment button. checkout – The “Checkout with Google Pay” payment button. donate – The “Donate with Google Pay” payment button. order – The “Order with Google Pay” payment button. pay – The “Pay with Google Pay” payment button. plain – The Google Pay payment button without the additional text. subscribe – The “Subscribe with Google Pay” payment button.
`button.buttonLocale`	String	The ISO 639-1 code representing the desired button language. Default value: The browser or operating system language settings. Allowed values: en, ar, bg, ca, cs, da, de, el, es, et, fi, fr, hr, id, it, ja, ko, ms, nl, no, pl, pt, ru, sk, sl, sr, sv, th, tr, uk, and zh.

Obtaining Google Pay token

The onTokenizationComplete function is called after the user approves the payment on the Google Pay form. The output contains the paymentData object (see Google Pay documentation) which is needed to request the Google Pay payment via the API from your backend.

Requesting Google Pay pay-in

To request the payment, use the Create a Google Pay PayIn endpoint. Include the Google Pay PaymentData and ensure that the SecureModeReturnURL parameter is set to https://checkout.mangopay.com.

Set up payment delegate – Assign a delegate function to the onCreatePayment attribute in your Google Pay options.
Handle payment authorization – After the user successfully authorizes a card for payment through the Google Pay sheet, the SDK will call your onCreatePayment function and pass the PaymentData to it.
Create pay-in – Implement the backend creation of the Google Pay PayIn on your server using the PaymentData provided.
Return pay-in object – After creating the pay-in, return the pay-in object to the SDK.

1 interface CreateGooglePayPaymentData {
2   PaymentData: string;
3   ProfilingAttemptReference: string;
4 }
5 
6 //Define GooglePay PayIn delegate
7 const handleCreateGooglePayPayIn = (data: CreateGooglePayPaymentData): Promise<CreateGooglePayPayInResult> => {
8 	return fetch(
9     'https://your-backend-api-url/create-googlepay-payin',
10     method: 'POST',
11     body: JSON.stringify(data)
12   );
13 };

Google Pay configuration example

1 const options = {
2   clientId: 'MANGOPAY_CLIENT_ID',
3 	environment: 'SANDBOX | PRODUCTION',
4 	paymentMethods: [
5 		{
6       type: 'google_pay',
7       options: {
8         merchantInfo: {
9 			    merchantId: 'test',
10 			    merchantName: 'Test',
11 			  },
12 				gateway: 'whenthen',
13 			  cardParameters: {
14 			    allowedAuthMethods: ['PAN_ONLY', 'CRYPTOGRAM_3DS'],
15 					allowedCardNetworks: ['VISA', 'MASTERCARD'],
16 			  },
17 			  transactionInfo: {
18 			    totalPrice: '20.00',
19 			    totalPriceStatus: 'FINAL',
20 			    currencyCode: 'EUR',
21 			    countryCode: 'DE', // required for EEA only
22 			    transactionId: '123456789',
23 			    totalPriceLabel: '20.00', // required if displayItems is provided
24 			    displayItems: [
25 			      {
26 			        label: 'PS5',
27 			        type: 'SUBTOTAL',
28 			        price: '20.00',
29 			      },
30 			    ],
31 			  },
32 			  paymentData: {
33 			    emailRequired: true,
34 			  },
35 			  onCreatePayment: (paymentData) => handleCreateGooglePayPayIn(paymentData),
36         button: {
37           buttonLocale: 'fr',
38           buttonType: 'book'
39         },
40       },
41     }
42 	]
43 };
44 
45 // Vanilla JS
46 const mangopaySdk = await CheckoutSdk.loadCheckoutSdk(elementOrSelector, options);
47 
48 // React.js
49 <MangopayCheckout ref={sdkRef} options={options} />

Configuring PayPal

Note – PayPal setup required

Offering PayPal requires approval from PayPal and activation. For more information, see the PayPal article.

PayPal configuration options

To configure PayPal, specify paypal as the type of the paymentMethods object. For the options, use the following configuration parameters.

Property Type Description

Property	Type	Description
`options.onCreatePayment`	Function REQUIRED	Use this attribute to request and return a PayPal pay-in. The assigned function should implement backend creation of the PayPal pay-in from your server.
`options.merchantId`	string REQUIRED	Unique identifier for your PayPal business account, required to process pay-ins. Production: Available in your PayPal Business Account Dashboard (Account Settings > Business information > Business profile, see PayPal help). Sandbox: Contact our support team to obtain.

options.onCreatePayment

Function REQUIRED

Use this attribute to request and return a PayPal pay-in.

The assigned function should implement backend creation of the PayPal pay-in from your server.

options.merchantId

string REQUIRED

Unique identifier for your PayPal business account, required to process pay-ins.

Production: Available in your PayPal Business Account Dashboard (Account Settings > Business information > Business profile, see PayPal help).
Sandbox: Contact our support team to obtain.

PayPal configuration example

1 //Define PayPal PayIn delegate
2 const createPayPalPayIn = (profilingAttemptReference: string): Promise<CreatePayPalPayInResult> => {
3 	return fetch(
4     'https://your-backend-api-url/create-paypal-payin',
5     body: JSON.stringify({ProfilingAttemptReference: profilingAttemptReference})
6   );
7 };
8 
9 const options = {
10     clientId: 'MANGOPAY_CLIENT_ID',
11     environment: 'SANDBOX | PRODUCTION',
12     amount: {
13         value: 1000,
14         currency: "EUR"
15     },
16     paymentMethods: [
17         {
18 	        type: "paypal",
19 	        options: {
20             merchantId: 'YOUR_PAYPAL_MERCHANT_ID', 
21 	          //define delegate to call when Paypal button is clicked
22 	          onCreatePayment: (data) => createPayPalPayIn(data)
23 	        }
24 	      }
25     ]
26 };
27 
28 const mangopaySdk = await CheckoutSdk.loadCheckoutSdk(elementOrSelector, options);
29 
30 //this event is triggered when redirect/payment is completed
31 mangopaySdk.on('paymentComplete', (event: CustomEvent<PaymentCompleteEventDetails>) => {
32     //  verify payment result
33     //  unmount checkout and present payment result.
34 });

Requesting PayPal pay-in

To request the payment, use the POST Create a PayPal PayIn endpoint. Ensure that the ReturnURL parameter is set to https://checkout.mangopay.com.

Configuring PayPal One-Click payments

PayPal One-Click allows returning customers to pay without re-entering their PayPal credentials. When enabled, the SDK displays a checkbox that lets customers opt in to save their PayPal account for future payments.

How it works

You configure the SDK with the clientToken (root-level, see below) and enableOneClick set to true (PayPal options)
The SDK renders a checkbox allowing the customer to opt in for one-click payments
When the customer completes the payment, onCreatePayment receives a second boolean argument indicating if the checkbox was checked
If true, your backend creates a Recurring PayIn Registration object and then a linked CIT pay-in
When the customer returns, the one-click payment experience is rendered automatically, allowing them to pay without logging in to PayPal
For the subsequent payments, you create a non-recurring PayPal pay-in

Prerequisites

Before implementing PayPal One-Click payments, you must have PayPal activated on your platform (see PayPal setup requirements).

Obtaining the clientToken

To initialize the SDK for PayPal One-Click, you need to obtain the clientToken as follows:

Contact Mangopay (via the Dashboard) to obtain a dedicated API key for use with clientToken features
From your server, call the POST Create an OAuth bearer token endpoint using the API key (with Basic authentication, encoding the string ClientId:ApiKey in Base64)
Using the access_token returned from the previous step, from your server call the POST Create an access token for Checkout SDK features using Bearer authentication

In response, the API returns another access_token which is the value to use as the clientToken when initializing the SDK for PayPal One-Click. The clientToken has a validity of 15 minutes, meaning the user must complete the transaction in that time.

PayPal One-Click configuration options

Property	Type	Description
`clientToken`	String REQUIRED	A token required for PayPal One-Click payments. This is a root-level SDK option (not part of the PayPal payment method options).
`options.enableOneClick`	Boolean	Set to `true` to enable the One-Click payment checkbox. When enabled, customers can opt in to save their PayPal account for future payments. Default value: `false`
`options.onCreatePayment`	Function REQUIRED	Function called when the customer initiates payment. Receives two arguments: `profilingAttemptReference` – Reference for fraud profiling `enableOneClick` – Boolean indicating if the customer checked the One-Click checkbox When `enableOneClick` is `true`, your backend should create a Recurring PayIn Registration object and then a linked CIT pay-in
`options.merchantId`	String REQUIRED	Your PayPal merchant account identifier. You can find your `merchantId` in your PayPal Business Account Dashboard.

Complete code example

1 // 1. Obtain clientToken from your backend
2 async function getClientToken() {
3   const response = await fetch('/api/get-client-token');
4   const data = await response.json();
5   return data.clientToken;
6 }
7 
8 // 2. Create PayPal payment on your backend
9 async function createPayPalPayment(profilingAttemptReference, enableOneClick) {
10   const response = await fetch('/api/create-paypal-payment', {
11     method: 'POST',
12     headers: { 'Content-Type': 'application/json' },
13     body: JSON.stringify({ 
14       profilingAttemptReference,
15       enableOneClick // If true, backend creates RecurringPayinRegistration + CIT
16     })
17   });
18   const data = await response.json();
19   return data.payInId;
20 }
21 
22 // 3. Initialize SDK with clientToken and enableOneClick
23 const clientToken = await getClientToken();
24 
25 const checkout = await MangopayCheckout.init({
26   clientId: 'your-mangopay-client-id',
27   clientToken: clientToken, // REQUIRED for one-click
28   environment: 'SANDBOX',
29   paymentMethods: [
30     {
31       type: 'paypal',
32       options: {
33         merchantId: 'YOUR_PAYPAL_MERCHANT_ID',
34         enableOneClick: true, // Enables the one-click checkbox
35         onCreatePayment: async (profilingAttemptReference, enableOneClick) => {
36           // enableOneClick is true if customer checked the checkbox
37           return createPayPalPayment(profilingAttemptReference, enableOneClick);
38         }
39       }
40     }
41   ]
42 });

Backend implementation

When enableOneClick is true, your backend should:

Call POST Create a Recurring PayIn Registration (PayPal) for the user
Call POST Create a Recurring PayPal PayIn with the CIT payload
Store the RecurringPayinRegistrationId for future one-click payments

For subsequent one-click payments for the user, call the non-recurring POST Create a PayPal PayIn endpoint.

Standard PayPal vs PayPal One-Click comparison

Feature	Standard PayPal	PayPal One-Click
Use case	One-off payments	Returning customers opting in to save PayPal
User experience	User logs in to PayPal each time	Checkbox to opt in; future payments skip PayPal login
SDK parameters	`onCreatePayment`, `merchantId`	`clientToken`, `enableOneClick`, `onCreatePayment`, `merchantId`
onCreatePayment arguments	`(profilingAttemptReference)`	`(profilingAttemptReference, enableOneClick)`
Backend action when opted in	POST Create a PayPal PayIn	POST Create a Recurring PayIn Registration and POST Create a Recurring PayPal PayIn with the CIT payload; then for subsequent payments byt the user POST Create a PayPal PayIn

Obtaining browser info for a pay-in

The browserInfo object is required when submitting a pay-in request. To get the required values for the transaction, use the getBrowserInfo function from the Checkout SDK instance. Pass on the values to your server.

1 //Using checkout-sdk or checkout-sdk-react package from npm.
2 import { getBrowserInfo } from '@mangopay/checkout-sdk'
3 
4 //alternatively, if you are using the cdn script
5 const mangopaySdk = await CheckoutSdk.loadCheckoutSdk('#container', options);
6 const browserInfo = mangopaySdk.getBrowserInfo();
7 
8 const payInRequestObj =
9 {
10 		...
11     browserInfo         : {
12         "AcceptHeader"  : browserInfo.AcceptHeader,
13         "JavaEnabled"   : browserInfo.JavaEnabled,
14         "Language"      : browserInfo.Language,
15         "ColorDepth"    : browserInfo.ColorDepth,
16         "ScreenHeight"  : browserInfo.ScreenHeight,
17         "ScreenWidth"   : browserInfo.ScreenWidth,
18         "TimeZoneOffset": browserInfo.TimeZoneOffset,
19         "UserAgent"     : browserInfo.UserAgent,
20         "JavascriptEnabled": browserInfo.JavascriptEnabled
21     }
22 };

Verifying the payment result

Once the onPaymentComplete event is triggered, verify the status of the relevant Mangopay API object:

Caution – Check payment result from backend

You should confirm the transaction result returned by the Checkout SDK by calling the Mangopay API from your backend.

Verify payment result

1 //This event is triggered by the SDK when a full payment cycle is complete.
2 mangopaySdk.on('paymentComplete', (event: CustomEvent<PaymentCompleteEventDetails>) => {
3 
4     const { Id } = event.details
5 
6     // 1. Verify payment result using the transaction Id.
7     // 2. Present payment result to user.
8 });

Showing and dismissing the loading spinner

When processing a token request, the SDK shows a loading spinner and retains it until the loading state is set to false. This provides a temporary state for the user until the full payment is complete, including calls from your platform’s backend.

The setLoading method handles the loading state for displaying and dismissing the spinner.

1 import { CheckoutSdk } from '@mangopay/checkout-sdk';
2 const mangopaySdk = await CheckoutSdk.loadCheckoutSdk('#container', options);
3 // dismiss the  loader spinner
4 mangopaySdk.setLoading(false);

Using Card Element

Card Element is a ready-made component that allows you to create your own card payment experience and tokenize card payment details. With Card Element, you can incorporate a custom pay button and have control over the tokenization process.

When using Card Element, you still benefit from card data validation, and the ability to customize the payment form.

Initialize the cardFormElement with your ClientId and select your environment (Sandbox or Production).

1 import { CheckoutSdk } from '@mangopay/checkout-sdk';
2 
3 const cardFormElement = await CheckoutSdk.loadCardFormElement(elementOrSelector, options);

cardFormElement-specific options

Property	Type	Description
`paymentMethod`	Object	The payment method used with the card form element. Only `'card'` is supported. See Configuring card payments section for details

Vanilla JS usage example

HTML

1 <body>
2     <form novalidate id="checkoutForm">
3         <div id="container"></div>
4         <button type="submit" id="submitButton">Pay now</button>
5     </form>
6     <script src="/index.js"></script>
7 </body>

TypeScript

1 import { CheckoutSdk } from '@mangopay/checkout-sdk';
2 
3 window.addEventListener('load', async () => {
4     const cardFormElement = await CheckoutSdk.loadCardFormElement('#container', options);
5     if (!cardFormElement) {
6         throw new Error('Failed to load MangopayCardFormElement');
7     }
8 
9     const submitButton = document.querySelector('#submitButton');
10     if (!submitButton) {
11         throw new Error('Submit button is missing.');
12     }
13 
14     submitButton.addEventListener('click', async (event) => {
15         event.preventDefault();
16         cardFormElement.disable();
17         try {
18             cardFormElement.completePayment();
19         } finally {
20             cardFormElement.enable();
21         }
22     });
23 
24     cardFormElement.on('error', (event: CustomEvent<ErrorEventDetails>) => console.error(event.detail));
25 
26     cardFormElement.on('tokenizationComplete', (event: CustomEvent<TokenizationCompleteEventDetails>) => {
27         // handle tokenization complete
28     });
29 });

ReactJS usage example

TypeScript

1 import { CardFormElement } from '@mangopay/checkout-sdk-react';
2 
3 const CheckoutFormComponent = () => {
4     const sdkRef = useRef(null);
5 
6     const onTokenizationComplete = () => {
7         /* Handle Card token here
8                e.g charge customer card using CardId
9         */
10     };
11 
12     return (
13         <>
14             <form noValidate>
15                 <CardFormElement
16                     ref={sdkRef}
17                     options={options}
18                     disabled={disabled}
19                     onError={onError}
20                     onLoaded={onLoaded}
21                     onChange={onChange}
22                     onTokenizationComplete={onTokenizationComplete}
23                 />
24             </form>
25             <button onClick={handleCompletePayment} className="btn pay-btn">
26                 Pay now
27             </button>
28         </>
29     );
30 }

Branding

You can customize the appearance of the checkout using the branding object.

TypeScript - Branding example

1 const options = {
2     branding: {
3         fontFamily: 'Helvetica Neue',
4         fontSize: {
5             primary: '14px',
6             secondary: '12px',
7         },
8         borderType: 'square', // 'square' | 'round' | 'bottom'
9         colors: {
10             primary: '#000000',
11             secondary: '#545A61',
12             accent: '#4E40EF',
13             accentContrast: '#FFFFFF',
14             border: '#E6E9EC',
15             borderFocused: '#000000',
16             error: '#EC0B43',
17         },
18         borderRadius: '0',
19         backgroundColor: '#ffffff',
20         textColor: '#000000',
21         lineHeight: '48px',
22         variables: undefined,
23         rules: undefined,
24     },
25 },
26 };
27 
28 // Vanilla JS
29 const mangopaySdk = await MangopaySdkLoader.loadCheckoutSdk('#container', options);
30 
31 // React.js
32 <MangopayCheckout ref={sdkRef} options={options} />

Theme variables and rules

You can use the rules and variables objects for further customization.

Variables

Variables are CSS variables that you can declare and use in your theme rules.

TypeScript

1 {
2     theme: {
3     ...,
4         variables: {
5             primaryColor: "#1D3557"
6             secondaryColor: "#457B9D"
7         }
8 
9         rules: {
10             PayButton: `
11             backgroundColor: var(--primaryColor);
12             `
13         }
14     }
15 }

Rules

Rules allows you to apply CSS styles to Checkout SDK components. To do so, target components by class names, with or without the CSS class selector prefix (FieldContainer or .FieldContainer), and specify the styles to apply. The feature supports all native CSS properties and nesting.

TypeScript

1 {
2     theme: {
3       ...,
4         variables: {
5             primaryColor: "#1D3557"
6             secondaryColor: "#457B9D"
7         }
8 
9         rules: {
10             '.FieldContainer': `
11               height: 40px;
12               border-radius: 8px;
13               backgroundColor: var(--primaryColor);
14               
15               &:hover {
16                 backgroundColor: var(--secondaryColor);
17               }
18           `
19         }
20     }
21 }

Localization

Mangopay Checkout SDK has built-in localization support for: DE, EN, ES, FR, NL, PT

TypeScript

1 const options = {
2     locale: 'en', // 'en' | 'fr' | 'es' | 'de' | 'pt' | 'nl' | Object
3 };
4 
5 // Vanilla JS
6 const mangopaySdk = await MangopaySdkLoader.loadCheckoutSdk('#container', options);
7 
8 // React.js
9 <MangopayCheckout ref={sdkRef} options={options} />

You can customize labels, placeholder and success and error messages by providing a customLanguage object.

1 const customLanguage = {
2   "card-information.header.label": "Card information",
3   "card.number.placeholder": "1234 1234 1234 1234",
4   "card.number.aria-label": "Card number",
5   "card.number.errors.required": "Card number is required",
6   "card.number.errors.min-length": "Minimum number of digits is 13",
7   "card.number.errors.invalid-number": "Invalid card number",
8 
9   "card.psp.legal.notice": "Processed with Mangopay",
10   "card.psp.legal.privacy": "Privacy.",
11   "card.save.label": "Save payment details for future use",
12   "card.saved-cards.choose-card.label": "Choose card",
13   "card.saved-cards.clear-card.label": "Clear",
14   "card.saved-cards.saved-card.aria-label": "The card ending in",
15   "card.billing-name.placeholder": "Name on card",
16   "card.billing-name.aria-label": "Name on card",
17   "card.billing-name.errors.required": "Full name is required",
18   "card.expiry.placeholder": "MM / YY",
19   "card.expiry.aria-label": "Card expiration",
20   "card.expiry.errors.required": "Expiration date is required",
21   "card.expiry.errors.pattern": "Expiration date format is not valid (MM/YY)",
22   "card.expiry.errors.expired": "Your card is expired",
23   "card.cvc.placeholder": "CVC",
24   "card.cvc.aria-label": "Card CVC",
25   "card.cvc.errors.required": "Security code is required",
26   "card.cvc.errors.min-length": "Security code is too short",
27   "card.cvc.errors.max-length": "Security code is too long",
28   "pay-button.label": "Pay",
29   "pay-button.aria-label": "Pay",
30   "payment-methods.card.label": "Card",
31   "payment-methods.show-less.label": "Show less",
32   "payment-methods.show-more.label": "Show more",
33   "payment-methods.applepay.label": "Apple Pay",
34   "payment-methods.applepay.aria-label": "Pay with Apple Pay",
35   "payment-methods.googlepay.label": "Google Pay",
36   "payment-methods.googlepay.aria-label": "Pay with Google Pay",
37   "payment-methods.paypal.label": "PayPal",
38   "payment-methods.paypal.aria-label": "Pay with PayPal",
39   "payment-methods.paypal.overlay.message": "Don’t see the secure paypal browser? We’ll help you re-launch the window to complete your purchase",
40   "payment-methods.paypal.overlay.continue": "Click to Continue",
41   "payment-success-state.label": "Payment Succeeded",
42   "redirect-note.label": "After submitting your order, you will be securely redirected to complete your purchase.",
43   "loading.label": "Processing your payment",
44 
45 	//errors
46   "error.invalid_cvc": "Invalid CVC",
47   "error.authorization_required": "Authorization Required",
48   "error.contact_card_issuer": "Contact Card Issuer",
49   "error.unsupported_card": "Unsupported Card",
50   "error.insufficient_funds": "Insufficient Funds",
51   "error.unsupported_currency": "Unsupported Currency",
52   "error.card_rejected": "Card Rejected",
53   "error.expired_card": "Expired Card",
54   "error.suspected_fraud": "Suspected Fraud",
55   "error.general_decline": "General Decline",
56   "error.incorrect_number": "Incorrect Number",
57   "error.incorrect_pin": "Incorrect Pin",
58   "error.invalid_address": "Invalid Address",
59   "error.invalid_card_or_account": "Invalid Card or Account",
60   "error.invalid_amount": "Invalid Amount",
61   "error.invalid_date": "Invalid Date",
62   "error.lost_restricted_or_stolen_card": "Lost, Restricted or Stolen Card",
63   "error.blocked_list": "Blocked List",
64   "error.not_permitted": "Not Permitted",
65   "error.offline_or_online_pin_required": "Offline or Online Pin Required",
66   "error.pin_retry_exceeded": "Pin Retry Exceeded",
67   "error.processing_error": "Processing Error",
68   "error.withdrawal_count_limit_exceeded": "Withdrawal Count Limit Exceeded",
69   "error.unknown": "Unknown error",
70   "error.fraud": "Fraud",
71   "error.three_d_secure": "3DS Failed",
72   "error.custom_rule": "Custom Rule",
73   "error.payment_cancelled": "Try making your payment again or select a different bank to continue",
74   "error.payment_rejected": "The payment was rejected by the institution. Try again, or select another account or institution",
75   "error.internal_server_error": "An unexpected error occurred",
76   "error.institution_not_responding": "This financial institution is not currently responding to requests. We apologize for the inconvenience",
77   "error.authorize.payment-already-authorized": "This payment has been already authorized",
78   "error.param_error": "One or several required parameters are missing or incorrect",
79   "error.payment_restart": "The payment wasn't successful, please try again",
80   "error.ressource_not_found": "The resource does not exist"
81 };
82 
83 const options = {
84   locale: customLanguage
85 };
86 
87 // Vanilla JS
88 const mangopaySdk = await CheckoutSdk.loadCheckoutSdk('#container', options);
89 
90 // React.js
91 <MangopayCheckout ref={sdkRef} options={options} />