# Recurring and Unscheduled Payments
## Overview
**Recurring Payments** allow you to charge a customer on a regular basis without requiring them to be present for each payment. This is particularly useful for subscription services or any scenario where you need to bill customers periodically.
**Unscheduled Payments** allow you to charge customers on an ad-hoc basis without the need for the customer to be present. This is ideal for businesses that need to process payments at irregular intervals or for one-off purchases.
Both Recurring and Unscheduled Payments require an initial payment to be processed with the customer present (CIT). This initial payment captures and securely stores the customer's payment details for future use. Subsequent payments can then be processed without the customer being present (MIT).
Processing Recurring and Unscheduled Payments using the embedded SDK involves a similar approach as described in this page.
## Requirements
Before you can process a Recurring or Unscheduled Payment, you must first set up an initial Payment Session with the customer present (CIT). This initial payment captures and securely stores the customer's payment details for future use. Subsequent payments can then be processed without the customer being present (MIT).
To set up such a Payment, you will need to follow the steps outlined in the [Initiate Recurring Payments](/documentation/get_started/initiate_payments/recurring) page or the [Initiate Unscheduled Payments](/documentation/get_started/initiate_payments/unscheduled) page, depending on your use case.
Once the Payment Session is created, you will have access to the `clientSecret` value, which is required to process the initial payment.
## Configuring the Embedded SDK
To process a Recurring or Unscheduled payment using the embedded SDK, you need to initialize the SDK with the appropriate configuration options. These include:
- The `clientSecret` obtained from the initial Payment Session
- Setting thecontroller's `paymentType` option to `Recurring` or `Unscheduled` depending on your use case
- The `accountId` option if you are processing the payment on behalf of a Sub-Account
Below is an example of how to configure the embedded SDK for processing Recurring or Unscheduled payments:
Recurring Payment
```javascript Process Recurring Payment Example
const controller = createController({
publicKey,
clientSecret,
// accountId, // If using the Platform Fee model
paymentType: "Recurring"
});
```
Unscheduled Payment
```javascript Process Unscheduled Payment Example
const controller = createController({
publicKey,
clientSecret,
// accountId, // If using the Platform Fee model
paymentType: "Unscheduled"
});
```
Provided that the embedded SDK is correctly configured, the embedded payment form will be rendered, allowing the customer to complete the initial payment.
## Complete Example
The following is a complete working example that combines:
- all the features covered in the [Quick Start](/documentation/get_started/process_payments/embedded_sdk_v3/quick_start#complete-example) guide
- the configuration for processing Recurring and Unscheduled payments as described above
```html Complete Example for Recurring and Unscheduled Payments
Ryft Card Form
```
## Next Steps
You should now have a basic payment form set up and be able to process Recurring or Unscheduled payments using the embedded SDK via a simple card form.
You can now explore additional features and customisation options offered by the SDK. Some recommended next steps include:
- Collecting additional information from the customer during checkout, such as billing/shipping address or custom fields. See the [Field Collection](/documentation/get_started/process_payments/embedded_sdk_v3/field_collection) page for more details on how to do this.
- Adding support for other payment methods like [Apple Pay](/documentation/get_started/process_payments/embedded_sdk_v3/apple_pay) and [Google Pay](/documentation/get_started/process_payments/embedded_sdk_v3/google_pay) to provide a seamless checkout experience for your customers.
- Enabling additional configuration options to further customise the payment form and flow according to your business needs. You can refer to the [Additional Configuration](/documentation/get_started/process_payments/embedded_sdk_v3/additional_config) page for more details on the available options and how to use them.
- Using the `checkout` component to easily enable multiple payment methods and additional features all in a single component. You can refer to the [Checkout Component](https://web-sdk.ryftpay.com/docs/web/latest/documents/checkout.html) page for more details.
- Handling SDK errors: Implement comprehensive error handling to manage different types of errors that may occur during the payment process, such as validation errors, network issues, or unexpected system errors. This will help you provide a better user experience and ensure that customers are informed about any issues that arise during checkout. You can refer to the [SDK Errors](/documentation/get_started/process_payments/sdk_errors) page for best practices and examples on how to implement effective error handling in your integration.
- Webhook handling: Set up webhooks to receive real-time notifications about payment events, such as successful payments, refunds, or chargebacks. This allows you to automate order fulfillment, update inventory, and keep customers informed about their transactions. You can refer to the [Webhooks documentation](/documentation/get_started/webhooks) for more details on how to set up and manage webhooks with Ryft.