# Subsequent request examples

## MIT Sale request

 - [POST /mit-sale](https://docs.upgate.com/openapi/subsequent-request-examples/mit_sale_request.md): This endpoint allows you to create a subsequent transaction using an existing payment token. It is typically used when you want to manage recurring or rebill payments on your side, or when you want to enable one-click payments for your customers without requiring them to re-enter their payment details.
To initiate a subsequent transaction, provide the payment token ID received from a previous Sale request.

## MIT Authorize request

 - [POST /mit-authorize](https://docs.upgate.com/openapi/subsequent-request-examples/mit_authorize_request.md)

## CIT Sale request

 - [POST /cit-sale](https://docs.upgate.com/openapi/subsequent-request-examples/cit_sale_request.md): TThis endpoint allows you to create a subsequent transaction that triggers a 3-D Secure (3DS) authentication flow for your users. It can be used when you want customers to actively confirm and provide consent for the charge, ensuring additional security and compliance with authentication requirements.
Similar to the standard subsequent transaction, this endpoint enables you to manage rebills on your end or offer one-click payments without requiring users to re-enter their card details.
Use the payment token ID received from the original Sale request to initiate this transaction.