---
title: "Transaction Types"
slug: "transaction-types"
updated: 2024-10-03T08:53:02Z
published: 2024-10-03T08:53:02Z
canonical: "docs.apcopay.com/transaction-types"
---

> ## 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.

# Transaction Types

Below are the **transaction types** we currently support. However, this could differ slightly depending on the acquirer selected.

### **Card Deposits**

| Transaction code | Description | Considerations| Supported Integration type |
| --- | --- | --- | --- |
| **AUTH*** <br>Authorisation| An 'authorisation' creates a validation on a card to verify its active status and ensure that there is a sufficient balance available to cover the requested amount. Proceed to process a capture (**'CAPT'**) to capturing the funds. | This only **blocks** the funds on a card. Consider using 'purchase'(**'PURC'**) if you wish to immediately trigger the capture process. An authorisation typically has a predefined expiration period, which is determined by the card issuer. The specific duration can vary but can remain active up to 30 days. After this period, the authorisation will expire automatically. | **`Hosted Payment Page`** or **`Payment Operations API`** |
| **CAPT** <br>Capture | A 'capture' refers to the action of recording and finalizing a previously authorized transaction, and initiating the transferring of funds from the customer's account to the merchant's account | Can only be used on an active authorisation transaction. | **`Payment Operations API`** |
| **PURC**<br>Purchase | A' purchase' merges both the authorisation and capture processes, validating the card's status, checking for sufficient funds, and finalizing the transaction by transferring the funds from the customer's card to the merchant's account | | **`Hosted Payment Page`** or **`Payment Operations API`**  |


**An **authorisation** has a predefined expiration period, which is determined by the card issuer. The specific duration can vary but typically remains active up to 30 days. After this period, the authorisation will expire automatically and any blocked funds will be released.*

You can view our API reference for using our Hosted Payment Page [here](https://apcopay.redoc.ly/#operation/CreateaHostedPaymentPageToken). Should you decide to use our payment APIs to process a card transaction click [here](https://apcopay.redoc.ly/#operation/PaymentOperationAUTHPURC).

### **Card Recurring Transactions**

Merchant-initiated transactions (MITs) enable purchases that are triggered by the merchant. This transaction type is commonly employed for recurring subscriptions or billings, where regular payments need to be captured automatically without direct customer involvement.

To process a recurring transaction, you can re-use the **`'Auth'`** or **` 'Purc'`** transaction type. As part of the payload, in the paymentsource object, you must select "TransactionReference" as the payment source along with the original PSP ID.

### **APM Deposits**

| Transaction code | Description | Supported Integration type |
| --- | --- | --- |
| **PURC**<br>Purchase | A purchase transaction type initiates the payment via the specified payment method. | **`Hosted Payment Page`** |

Due to the nature of the APMs, only purchase transaction types are supported. This means that once the payment is completed, the settlement of funds to the merchant is immediately initiated without the need of processing a capture.

You can view a list of detailed specifications of all our APMs [here](/v1/docs/apm-specifications).

### **Refunds and Payouts**

| Transaction code | Description | Supported Integration type |
| --- | --- | --- |
| **PARTIALREFUND** | This transaction type is to be used for both partial and full refund. Its important the refund amount does not exceed the `Purchase` or `Captured` amount.| **`Payment Operations API`** |
|**ORIGINALCREDIT** | Used to request Original Credit Transfers (OCTs) or Payouts to payment instruments not limited to the deposit amount. | **`Payment Operations API`** |

You can refer to these dedicated pages for [refunds](/v1/docs/refund-a-payment) and [payouts](/v1/docs/request-payouts).

### **Voids**

Voids are available only for card payments, typically on Authorisations, depending on your acquirer. For details specific to your chosen acquirer, please contact our [support team](/v1/docs/contacting-apcopay).

| Transaction code | Description | Supported Integration type |
| --- | --- | --- |
| **GENERALVOID** | This transaction type reverses a previously authoirsed card transaction   | **`Payment Operations API`** |

This is usually only possible in the first 24 hours of the authorisation. For more specifics please contact our [Contact Us](/v1/docs/contacting-apcopay).

Please refer to this dedicate [page](/v1/docs/void-a-card-payment).