# Getting Started

## Integration using Components

Using Components is more complicated than using Checkout - yet, it allows you to have full control over the look and feel of the payment form and integrate it more seamlessly into your website.

For more information, please go to the [Components tutorial](/docs/using-components).

## Integration using Checkout

Using Checkout allows for the fastest and easiest integration, as all the hard work is handled by Shift4.

For more information, please go to the [Checkout tutorial](/docs/checkout/using-checkout-session).

Please check our guidelines for CSP [here](/docs/csp-integration).

## Next steps

### Saving cards for later use

To save card data for later use, you need to create [a customer](/docs/api/shift4-gateway/customers/createcustomer) and use it to save [a card](/docs/api/shift4-gateway/cards/createcard). That card can be later used to create multiple charges - without requiring the user to retype his card data ([read more](/docs/charging-cards)).

### Creating automatically recurring subscriptions

When you already have a customer with a saved card - it is easy to start charging that customer periodically. To do so, two things are necessary. The first one is [a plan](/docs/api/shift4-gateway/plans/createplan) that defines how much and how often the card will be charged. The second thing is [a subscription](/docs/api/shift4-gateway/subscriptions/createsubscription) that combines a customer with a plan.

### Receiving events

Once you start using advanced features like subscriptions, you may want to be notified about events that occurred in the system, not as a result of your direct actions. An example of such an event could be the automatic creation of a charge due to a subscription entering the next billing cycle. Another example could be a customer starting a dispute over the charge that you made. If you are interested in receiving events read more about [webhooks](/docs/webhooks).