❗️
Passing credit card data directly through this endpoint requires PCI SAQ D compliance.

🚧
Please review these guides for more information about your specific use case
The Capture API encompasses a wide range of use cases and integrates into various scenarios. To ensure seamless integration into your solution, please consult the appropriate guide below before beginning your development:

Recurring Payments via the Capture API

3DS - customerNo is mandatory in this workflow

📘
Side notes

To explore the full list of available payment methods, please check this link Available Payment Methods - PayIns

When 3DS is enabled, an authUrl will be returned in the response. You’ll need to manually redirect the user to that URL to complete the authentication step. After the redirection, the user will complete the transaction on that page. The final status will be sent via webhook, configured through the ipnUrl parameter in your request.

To enable 3DS on your account, please contact the Solutions team.

In recurring payments (vautling), after calling the capture api the webhook will have the vaultId.

goodsInfo

The goodsInfo field is recommended to help merchants with disputes. It is an object with the following fields:

Field	M/O/C	Description
amount	M	The item price or rate per unit, can not be a negative number.
category	M	The item category type. Possible values: DIGITAL_GOODS, PHYSICAL_GOODS
description	M	The detailed item description.
goods_info	M	The item name or title.
tax	O	The item tax for each unit.
quantity	M	The item quantity.

Note When adding to the goodsInfo, make sure to include the goodsInfo as a string. (ex. "{"goods_name":"test","quantity":"1","category":"DIGITAL_GOODS","description":"testing","amount":"300","tax":"0"}")