# Checkout

Create your own uniquely styled and branded checkout form by integrating our SDK into your website and native apps.

br
**Supported payment methods**: *American Express / Carte Bancaires / Discover / Diners / EFTPOS / ELO / JCB / Maestro / MasterCard / MasterCard Debit / Visa / Visa Debit / Visa Electron (UK only)*

## What is Checkout?

Checkout is the first step of the payment journey. You can use it with different Access APIs to complete the flow you need. The Access Checkout SDK processes and stores card details, and provides you with encrypted sessions. You can then either apply the session directly in the [Payments API](/products/payments/card-payment) or [create a token](/products/verified-tokens/create-verified-token) for use with our Modular APIs.

Note
If you are managing cardholder data in your own environment, you must comply with the necessary PCI DSS requirements.

### What is a session

A  `session` is a unique identifier for your customer's payment details, generated by the SDK.

Prerequisite
In order to use our Checkout SDK you will need a checkout ID.

- **Enterprise**: this will be given to you by your Implementation Manager as part of onboarding
- **SMB (Worldpay eCommerce)**: retrieve this from your [Dashboard Portal](https://dashboard.worldpay.com/)


## Supported payment journeys

Payments API
Enterprise

SMB (Worldpay eCommerce)

#### Pay with a new card:

The SDK generates a card session containing the card number, expiry and CVC. Apply the session in the Payments API request.

#### Pay with a stored card and CVC:

The SDK generates a session containing only the CVC. Apply this along with a token as part of a stored card journey.

Modular APIs
Enterprise

#### Pay with a new card:

After the SDK generates the session, Worldpay verifies the card details and then stores the card number and expiry date as a reusable verified token. Most card issuers only need the card number, expiry date and account details to take a payment.

Once the CVC is used for card verification, it is **not** stored - this is in line with PCI compliance. So when you take a payment, CVC is **not** submitted in the payment authorization request.

#### Pay with a new card and CVC:

Gain extra security while taking a payment by submitting the CVC in the payment authorization request.

As well as using the session to verify the card details and create a verified token, Worldpay creates an additional encrypted session to capture the CVC number. This CVC session is stored for 15 minutes.

#### Pay with a stored card and CVC:

You can use the SDK to generate an encrypted CVC session only. You can then take a payment using this session along with a previously created verified token.

## Our SDKs

Web SDK
Add JavaScript to your checkout

Android SDK
Set up your Android application

iOS SDK
Set up your iOS application

React Native SDK
Set up your React Native application