---
title: "Authorisation:Capture"
method: PATCH
path: "/transactions/{transactionId}/capture"
tags: ["Transactions"]
---

# Authorisation:Capture

`PATCH /transactions/{transactionId}/capture`

Transactions that have the status authorize (is used by credit card payments or Buy now, Pay later payments) needs an extra action to convert the payment state to a PAID (100) transaction. This can be achieved by capturing the transaction. You can use the EX code or the order Id to capture the transaction

## Path parameters

- `transactionId` Id, required — unresolved $ref

## Request body

- object
  - `amount` Value — unresolved $ref
  - `products` object

## Response `200`

Ok.

- TransactionStatus
  - `id` string — The Id of the transaction.
  - `orderId` string — The orderId of the transaction.
  - `serviceCode` string — The ID of your service. You can find the service ID in the portal.
  - `description` string — Is shown on the statement of the payer.
  - `reference` string — The merchant identification of this transaction. This field only allows alphanumeric characters
  - `ipAddress` string — An ip address
  - `amount` Amount
    - `value` integer, required — The amount in cents.
    - `currency` string — The currency in ISO-4217 format.
  - `amountConverted` Amount
    - `value` integer, required — The amount in cents.
    - `currency` string — The currency in ISO-4217 format.
  - `amountPaid` Amount
    - `value` integer, required — The amount in cents.
    - `currency` string — The currency in ISO-4217 format.
  - `amountRefunded` Amount
    - `value` integer, required — The amount in cents.
    - `currency` string — The currency in ISO-4217 format.
  - `status` Status
    - `code` integer — The status code.
    - `action` string — The state in which the transaction resides
    - `phase` string — The current phase in the transaction state
  - `paymentData` TransactionStatusPaymentData
    - `method` string — Payment method of the transaction.
    - `customerKey` string — Customer key of the customer from the transaction.
    - `customerId` string — Customer id of the customer from the transaction.
    - `customerName` string — Customer name of the customer from the transaction.
    - `ipAddress` string — Ip address of the customer from the transaction.
    - `secureStatus` boolean — Secure status of the transaction.
    - `paymentVerificationMethod` integer
  - `paymentMethod` TransactionStatusPaymentMethod
    - `id` integer — The ID of the payment option e.g. iDEAL is 10. See: services/get/sl-xxxx-xxx.
    - `subId` integer — The chosen sub ID of the payment option e.g. The bank id for iDEAL. See: services/get/sl-xxxx-xxx.
  - `integration` Integration
    - `testMode` boolean — Indicates if the service is in testmode or not, possible values: false or true
  - `expiredAt` string, date-time, nullable — Expire date in the correct ISO-8601 (a.k.a. ATOM) notation.
  - `createdAt` CreatedAt — unresolved $ref
  - `createdBy` CreatedBy — unresolved $ref
  - `modifiedAt` ModifiedAt — unresolved $ref
  - `modifiedBy` ModifiedBy — unresolved $ref
  - `deletedAt` DeletedAt — unresolved $ref
  - `deletedBy` DeletedBy — unresolved $ref

## Other responses

- `400` — Bad request, see response body for more information
- `401` — Unauthorized. Supplied credentials are invalid
- `403` — Forbidden. Supplied credentials have no rights
- `404` — Resource not found
- `405` — Used HTTP method is not allowed
- `406` — Not acceptable. The supplied content type in the accept parameter in the header is not supported
- `422` — Unprocessable entity, see response body for more information
- `429` — Rate limit reached.
- `500` — An internal error occurred

---

[API](https://skmtc.dev/pay/apis/pay-transaction-gateway-unit-api.md) · [All operations](https://skmtc.dev/pay/apis/pay-transaction-gateway-unit-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/pay/pay-transaction-gateway-unit-api/revisions/2bc260c7bdfc/schema)