> For the complete documentation index, see [llms.txt](https://developers.frontstream.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.frontstream.com/argofire/introduction-to-payment-processing/supported-payment-methods.md).

# Supported Payment Methods

<figure><img src="/files/OPkpKWNGisTRODxR9jdP" alt=""><figcaption></figcaption></figure>

**ArgoFire** supports multiple secure, tokenizable payment methods for processing purchases, one-time payments, and recurring sales. All methods integrate seamlessly with ArgoFire’s PCI-compliant tokenization, repeat payment, and recurring billing infrastructure.

***

#### 1. Credit Cards

ArgoFire supports all major credit card brands:

* Visa
* Mastercard
* American Express
* Discover

**Usage**

* Tokenized via `GetToken()`
* Processed via `ProcessCreditCard`
* Can be used for one-time or recurring sales
* Stored securely for repeat sales using `ManageCreditCardInfo`

***

#### 2. Debit Cards

**Usage**\
Most branded debit cards (e.g., Visa Debit, Mastercard Debit) are processed as credit card transactions—commonly referred to as **offline debit**. These transactions follow the same flows as credit card sales, including tokenization, authorization, and settlement.

In contrast, **PIN-based (online) debit cards** are also supported, but their availability and processing behavior vary by processor. PIN debit may require additional configuration and does not follow the standard credit card transaction flow.

***

#### 3. ACH / eChecks (Bank Transfers)

ArgoFire supports ACH direct debit from U.S. bank accounts.

**Usage**

* Tokenized via `GetCheckToken()`
* Processed via `ProcessCheck`
* Can be used for one-time or recurring sales
* Stored securely using `ManageCheckInfo`

Please see more details of these **ProcessCredit, ProcessCheck, and ProcessDebitCard** APIs here:

{% content-ref url="/pages/BiSh52nhhp5VYx1eTKHE" %}
[Payment Processing – Credit, Check, Debit](/argofire/full-endpoint-reference-and-tools/payment-processing-credit-check-debit.md)
{% endcontent-ref %}

Please find more information about our Tokenization Services here:

{% content-ref url="/pages/y20bxK0h6FsOYuiXkxRg" %}
[Tokenization Services](/argofire/full-endpoint-reference-and-tools/tokenization-services.md)
{% endcontent-ref %}

***

**4. Digital Wallets (Apple Pay & Google Pay)**

Apple Pay and Google Pay are supported in specific integration contexts within **ArgoFire**.\
These payment methods can be used by partners whose implementations pass transactions to the `ProcessCreditCard` endpoint, provided the wallet payload is formatted and submitted correctly.

* Repeat sales and recurring billing using digital wallets (Apple Pay, Google Pay) are **not currently supported in ArgoFire** but are planned for future updates.
* For **ECOMM transactions**, any follow-on transaction (Repeat Sale or Recurring) must also be processed as ECOMM since digital wallet cryptograms are acquired through a web-based flow.
* **MOTO transactions** generally do not support digital wallets due to authentication requirements.
* Processor-specific availability may vary and should be confirmed prior to launch.

For **Digital Wallet** support we recommend implementing our **Embedded Payment Form** versus direct integration.

Please see our Embedded Payment Form implementation guide:

{% embed url="<https://developers.frontstream.com/introducing-our-embedded-form/how-to-implement>" %}

***

#### Unsupported Payment Types (via API)

The following are **not supported** through the ArgoFire Secure Electronic Payments API:

* PayPal
* Buy Now, Pay Later services (e.g., Klarna, Afterpay)
* Cryptocurrency

#### Summary Table

| Payment Method         | API Tokenization | Repeat Sales                                                                                                  | Recurring Billing                                                                                             | Endpoint(s)                     |
| ---------------------- | ---------------- | ------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- | ------------------------------- |
| Credit Card            | ✅                | ✅                                                                                                             | ✅                                                                                                             | `GetToken`, `ProcessCreditCard` |
| Debit Card             | ✅ (as credit)    | ✅                                                                                                             | ✅                                                                                                             | `GetToken`, `ProcessCreditCard` |
| ACH / eCheck           | ✅                | ✅                                                                                                             | ✅                                                                                                             | `GetCheckToken`, `ProcessCheck` |
| Apple Pay / Google Pay | ✅                | <mark style="color:red;">🚧</mark> <mark style="color:red;"></mark>*<mark style="color:red;">(future)</mark>* | <mark style="color:red;">🚧</mark> <mark style="color:red;"></mark>*<mark style="color:red;">(future)</mark>* | `ProcessCreditCar`              |

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developers.frontstream.com/argofire/introduction-to-payment-processing/supported-payment-methods.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.