# Payment Flows & User Experience

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

### How ArgoFire Handles Payment Flows & Use Cases

**ArgoFire** delivers flexible and secure payment processing through a powerful API and web-based virtual terminal, built to meet the needs of merchants and commerce platforms. From recurring billing to secure token reuse, ArgoFire provides a dependable backend for a wide range of real-world payment scenarios.

***

#### Use Case: One-Time Payment via Direct API Integration

1. **Frontend Collection**\
   Your platform collects payment data from the user using a secure, PCI-compliant input method.
2. **API Submission**\
   Payment details are passed to ArgoFire's API for immediate processing.
3. **Authorization & Settlement**\
   ArgoFire authorizes the transaction and routes it to the appropriate payment processor for settlement.

See how One-Time Payment API looks:

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

Use Case: Recurring Payment Setup via API

1. **Customer Enrollment**\
   A customer signs up for a recurring payment plan on your site, providing payment details and selecting a billing frequency (e.g., monthly, annually).
2. **Token Generation**\
   ArgoFire tokenizes the payment credentials and securely stores them for future transactions.
3. **Schedule Configuration**\
   A recurring billing schedule is created and linked to the token, with parameters such as start date, amount, and frequency.
4. **Automated Billing**\
   ArgoFire processes the payment automatically at the defined interval.
5. **Profile Management**\
   Recurring payment profiles can be updated or canceled via API or ArgoFire’s admin interface.

See how a Recurring Payment API looks:

{% content-ref url="/pages/BALA2QJwJGuePOQbSsTj" %}
[Recurring Billing & Customer Info](/argofire/recurring-billing-and-customer-info.md)
{% endcontent-ref %}

Use Case: One-Click Repeat Payment with Stored Token

1. **Initial Tokenization**\
   After a successful payment, ArgoFire returns a token representing the customer's payment method.
2. **Stored Credentials**\
   Your system securely stores the token for future use, never handling raw card or bank data.
3. **Initiate Repeat Charge**\
   When the customer returns, your system uses the stored token to initiate a new charge through the API—eliminating the need to re-enter payment details.
4. **Response Handling**\
   You receive confirmation details, including transaction ID, status, and receipt metadata.

More about our Tokenization processing:

{% content-ref url="/pages/rS5OteIyDWawYZdh4Gmv" %}
[Tokenization & Repeat Transactions](/argofire/key-concepts-and-features/tokenization-and-repeat-transactions.md)
{% endcontent-ref %}

***

Use Case: Manual Payment Entry via Virtual Terminal

1. **Merchant Login**\
   Staff access ArgoFire’s secure virtual terminal interface via browser.
2. **Manual Entry**\
   A user inputs customer information and enters card or bank payment details—commonly used for mail order, phone orders, or in-house payments.
3. **Secure Processing**\
   ArgoFire processes the payment immediately, ensuring compliance with PCI requirements.
4. **Confirmation & Receipt**\
   A confirmation screen is displayed, and a receipt can be emailed directly to the customer.

More about our Virtual Terminal processing:

{% content-ref url="/pages/azaqdboda3fQ3rffgobu" %}
[Virtual Terminal](/argofire/virtual-terminal.md)
{% endcontent-ref %}

***

#### Why These Flows Matter

* **API-First Approach:** Build fully customized checkout and payment experiences using ArgoFire’s secure, developer-friendly endpoints.
* **Built-In Recurring Support:** Schedule and manage automated billing without relying on a separate subscription service.
* **Tokenization for Reuse:** Make repeat purchases fast and secure using ArgoFire-generated tokens.
* **Virtual Terminal for Admins:** Enable staff to handle back-office donations securely and efficiently.
* **Secure & Compliant:** ArgoFire ensures PCI-compliant handling of payment data through tokenization, encryption, and secure infrastructure.


---

# Agent Instructions: 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:

```
GET https://developers.frontstream.com/argofire/introduction-to-payment-processing/payment-flows-and-user-experience.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.