---
title: "Initiate a Stored Card Payment"
slug: "initiate-a-stored-card-payment"
updated: 2025-02-20T15:02:28Z
published: 2025-02-20T15:02:28Z
canonical: "docs.apcopay.com/initiate-a-stored-card-payment"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apcopay.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Initiate a Stored Card Payment

If a customer opts to store their card details during a transaction, you can utilise the saved information for future payments, eliminating the need for them to input their details again.

They are two types of Stored Card Payments

- A **Customer-Initiated Transaction (CIT)** allows customers to bypass the inconvenience of entering their card details repeatedly for future purchases. When a customer wishes to make a subsequent payment, they can simply select a previously used card.
</br>

- **Merchant-Initiated Transaction (MIT)** -  With a Merchant-Initiated Transaction, you have the flexibility to store a customer's card details during the initial transaction and utilise them for subsequent transactions at a later date. MITs are commonly employed in subscription-based models or for paying recurring bills. 

:::(Info) (Important Info related to MITs)
To use MIT transactions, your acquirer needs to approve your request to process MIT transactions. For more information, please reach out to our [support team](/v1/docs/contacting-apcopay).
:::

You can perform a **CIT** by using the below endpoint.

<div style="display: flex; justify-content: space-between; align-items: center; border: 1px solid #e0e0e0; padding: 10px; background-color: #f5f5f5;">
    <strong style="background-color: #1F5CA6; color: #fff; padding: 5px; border-radius: 3px;">POST</strong>
    <strong style="margin-left: 10px; flex: 1;">/api/directconnect/execute</strong>
    <a href="https://apcopay.redoc.ly/#operation/PaymentOperationAUTHPURC" target="_blank" style="margin-left: 10px;">Try it here</a>
    <br>
    <br>
</div>
</br>

**Using the Card Token**

An `AUTH` or `PURC` using a [card token](/v1/docs/authorise-a-payment).

If you are using our `hosted payment page`, a `card token` is returned on a **processed** payment notification once the transaction is completed.

You can then request a transaction using the above mentioned endpoint. Its important you use the `cardtoken` as the `PaymentSource` in the `PaymentCredentials` node.
<br>

**Using the PSP ID**

-  An `AUTH` or `PURC` using a [PSP ID](/v1/docs/authorise-a-payment).

You can then request a transaction using the above mentioned endpoint. Its important you use the `TransactionReference` as the `PaymentSource` in the `PaymentCredentials` node.

**Using the Card PAN ( requires the PCI DSS SAQ Level D )**

    - If you are using our `direct connect solution`, click [here](/v1/docs/tokenise-a-payment-card) for a dedicated page on our card tokenisation APIs.
 
 You can then request a transaction using the above mentioned endpoint. Its important you use the `TransactionReference` as the `PaymentSource` in the `PaymentCredentials` node.
<br>


:::(Warning) (3D Secure)
Cardholder-Initiated Transactions (CIT) may be subject to 3D Secure Authentication in certain jurisdictions and with specific card issuers. When this applies, the response from your transaction request will include a redirection URL. You must redirect the customer to this URL to complete the authorization process.
:::

<br>

**MIT** transaction can be initatied by:
- An `AUTH` or `PURC` using a [card token](/v1/docs/authorise-a-payment).
    - If you are using our `hosted payment page`, a `card token` is returned on a 'processed' callback notification once the transaction is completed.
    - If you are using our `direct connect solution` via our `Payment Operations APIs`, click [here](/v1/docs/tokenise-a-payment-card) for a dedicated page on our card tokenisation APIs.
-  An `AUTH` or `PURC` using a [PSP ID](/v1/docs/authorise-a-payment).