# Card payment integration
> This document provides a consolidated overview of card payment integration requirements, features, and key considerations across Antom products.
This document provides a consolidated overview of card payment integration requirements, features, and key considerations across Antom products.
## Supported card types {#supported_card}
Antom offers a wide ranges of cards, allowing you to accept both global cards and local cards. Global cards include bank cards issued by international card scheme for global buyers. Local cards include bank cards issued for specific regions. Refer to [Cards](https://docs.antom.com/ac/antomop/card_overview.md) to view the full list of supported card types.
## Integration options {#card_integration}
Antom offers multiple integration paths, such as Payment Element, Checkout Page (CKP), hosted API, and end-to-end API integration. You can choose the one that best fits your business needs.
For the end-to-end integration mode, which is suitable for merchants with high requirements for payment process customization, you must be PCI-qualified. You are required to provide the relevant materials based on your business needs to complete the verification:
- If your annual card transaction volume is expected to exceed 6 million, complete and submit the [PCI Attestation of Compliance (AoC)](https://docs-prv.pcisecuritystandards.org/PCI%20DSS/Reporting%20Template%20or%20Form/PCI-DSS-v4-0-ROC-AOC-Merchants-r1.pdf) file for verification.
- If your annual card transaction volume is expected to be below 6 million, complete and submit the [PCI DSS Self-Assessment Questionnaires (SAQs)](https://docs-prv.pcisecuritystandards.org/SAQ%20(Assessment)/SAQ/PCI-DSS-v4-0-SAQ-D-Merchant-r1.pdf) file for verification.
For more information about PCI DSS compliance requirements, see [PCI DSS standard](https://www.pcisecuritystandards.org/).
#### Payment Element
Embedded payment components Drop-in UI components that embed directly into your application. Provides a native payment experience.
Key capabilities ● No page redirects required ● Pre-built, customizable UI ● Requires client-side integration [One-time Payments](https://docs.antom.com/ac/cashierpay/overview.md) - [Payment Element integration guide](https://docs.antom.com/ac/cashierpay/element.md?platform=web-wap)
- [Appearance customization](https://docs.antom.com/ac/cashierpay/appearance.md)
[Subscription Payment](https://docs.antom.com/ac/subscriptionpay/overview.md) - [Payment Element integration guide](https://docs.antom.com/ac/subscriptionpay/element_subscription.md?platform=web-wap)
#### Checkout Page (CKP)
⚡ Fastest setup Hosted payment page Redirect customers to a secure, Antom-hosted payment page. Fastest path to going live with minimal development effort required.
Key capabilities ● Minimal code needed ● Automatic payment method display ● Requires page redirect [One-time Payments](https://docs.antom.com/ac/cashierpay/overview.md) - [Hosted Checkout Page (CKP)](https://docs.antom.com/ac/cashierpay/HOSTEDCKP.md)
- [Embedded Checkout Page (CKP)](https://docs.antom.com/ac/cashierpay/embeddedckp.md)
[Subscription Payment](https://docs.antom.com/ac/subscriptionpay/overview.md) - [Hosted Checkout Page (CKP)](https://docs.antom.com/ac/subscriptionpay/HOSTEDCKP_subscription.md)
#### API-only
🔧 Advanced Custom payment page Build a fully customized payment experience by making API calls to obtain redirect URL to corresponding payment method pages. Complete control over UI and user flow at the cost of increased complexity.
Key capabilities ● Seamless user experience directing buyers to a specific payment method page ● Require manual integration for each payment method ● Require PCI qualifications [One-time Payments](https://docs.antom.com/ac/cashierpay/overview.md) - [Hosted API integration guide](https://docs.antom.com/ac/cashierpay/cardcollant.md)
- [End-to-end API integration guide](https://docs.antom.com/ac/cashierpay/cardinfocallmerchant.md)
[Subscription Payment](https://docs.antom.com/ac/subscriptionpay/overview.md) - [Hosted API integration guide](https://docs.antom.com/ac/subscription/cardcollant_subscription.md)
- [End-to-end API integration guide](https://docs.antom.com/ac/subscriptionpay/cardinfocallmerchant_subscription.md)
#### Store a card independantly
Standalone card binding Build a fully customized card binding experience via SDK integration or API calling to enable your buyers to save their cards at any stage of the payment process. In subsequent transactions, you can use the token of the stored card to initiate payments without collecting the buyer's card details again.
Key capabilities ● Seamless user experience directing buyers to a card storing page ● Require PCI qualifications for end-to-end API integration API integration - [Integration guide (API)](https://docs.antom.com/ac/pm/cv.md)
SDK integration - [Integration guide (SDK)](https://docs.antom.com/ac/pm/cvsdk.md)
---
## Integration key considerations {#key_considerations}
When you integrate global or local cards through the end-to-end API path, you are required to obtain PCI DSS qualifications, and you must pass in the following parameters.
### Global cards {#global}
The table below lists the key parameters for processing payments with international cards such as Visa, Mastercard, American Express, and more:
| **Parameter name** | **Description** | **Remark** |
| --- | --- | --- |
| *paymentMethod.paymentMethodMetaData.cardNo* | Plaintext card number. Collected by the merchant from the buyer. | Required |
| *paymentMethod.paymentMethodMetaData.expiryYear* | Card expiration year. Format: two-digit year (e.g., `24` for 2024). | Required |
| *paymentMethod.paymentMethodMetaData.expiryMonth* | Card expiration month. Format: two-digit month (e.g., `09` for September). | Required |
| *paymentMethod.paymentMethodMetaData.cvv* | Card Security Code (CVV). | Recommended to pass in during first-time payments; do not pass in for [COF](https://docs.antom.com/ac/pm/cof) scenarios. |
| *paymentMethod.paymentMethodMetaData.cardholderName* | Cardholder name. Only English names are supported. | Required |
| *paymentMethod.paymentMethodMetaData.billingAddress* | Billing address associated with the cardholder's account. | Optional (Recommended for `US`, `CA`, `UK` issuing countries) |
### Local cards {#local}
The following table lists the key parameters for processing payments with local card brands in specific countries/regions:
| **Parameter name** | **Description** | **Whether required** | | | | | |
| --- | --- | --- | --- | --- | --- | --- | --- |
| **South Korean cards** | **Brazilian cards** | **Chilean cards** | **Mexican cards** | **Peruvian cards** | **Turkish cards** | | |
| *paymentMethod.paymentMethodMetaData.cardNo* | Plaintext card number. Collected by the merchant from the buyer. | Yes | Yes | Yes | Yes | Yes | Yes |
| *paymentMethod.paymentMethodMetaData.expiryYear* | Card expiration year. Format: two-digit year (e.g., `24` for 2024). | Yes | Yes | Yes | Yes | Yes | Yes |
| *paymentMethod.paymentMethodMetaData.expiryMonth* | Card expiration month. Format: two-digit month (e.g., `09` for September). | Yes | Yes | Yes | Yes | Yes | Yes |
| *paymentMethod.paymentMethodMetaData.cvv* | Card Security Code (CVV). | No | Yes | Yes | Yes | Yes | Yes |
| *paymentMethod.paymentMethodMetaData.cardholderName* | Cardholder name. Only English names are supported. | No | Yes | Recommended | Recommended | Recommended | Yes |
| *paymentMethod.paymentMethodMetaData.dateOfBirth* | Cardholder's date of birth. Format: `YYYY-MM-DD`. | YesNote 1 | No | No | No | No | No |
| *paymentMethod.paymentMethodMetaData.cardPasswordDigest* | First two digits of the card payment password. | Yes | No | No | No | No | No |
| *paymentMethod.paymentMethodMetaData.businessNo* | 10-digit business number for corporate cards. | Yes | No | No | No | No | No |
| *paymentMethod.paymentMethodMetaData.cpf* | Brazilian individual taxpayer identification number. | No | ConditionalNote 2 | No | No | No | No |
| *paymentMethod.paymentMethodMetaData.payerEmail* | Payer's email address. | No | Yes | Yes | Yes | Yes | No |
> **[INFO]** **Note**: 1. Required for South Korean individual cards.
> 2. Required for cross-border transactions; optional for local transactions
## Card features {#features}
Antom card payment solution offers a comprehensive, secure, and intelligent suite of payment features designed to optimize payment processes, boost conversion rates, and ensure transaction security worldwide. You can integrate the following features that meet your business needs:
- [3D Secure 2](https://docs.antom.com/ac/pm/3ds.md): Antom card payments support the 3D Secure 2 authentication protocol, helping you comply with PSD2 Strong Customer Authentication (SCA) regulations while mitigating fraud and chargeback risks through liability shift mechanisms.
- [Antom 3DS-Retry](https://docs.antom.com/ac/pm/3ds_retry.md): Antom 3DS-Retry feature automatically retries soft-declined transactions or initiates the 3DS authentication process.
- [Merchant-Initiated Transaction (MIT)](https://docs.antom.com/ac/pm/mit.md): To accommodate diverse scenarios, Antom provides Merchant-Initiated Transactions (MIT) for subscriptions and recurring payments.
- [Installments](https://docs.antom.com/ac/pm/installment.md): Antom supports flexible installment options to help enhance your buyers' purchasing will.
- [Antom Tokenization](https://docs.antom.com/ac/pm/tokenization.md): With Antom Tokenization technology, customers enjoy a seamless one-click payment experience, significantly improving repeat purchase rates and payment success rates.
- [Card-on-File (COF) transactions](https://docs.antom.com/ac/pm/cof.md): COF (Card-on-File) refers to a card that the buyer has previously used for payment and stored at the merchant's site during a transaction.
- [Co-badged cards](https://docs.antom.com/ac/pm/co-badged_cards.md): For co-badged card payments, Antom delivers full compliance support and brand selection capabilities, ensuring secure, compliant, and efficient acceptance of various card payments in global markets.