> 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/introducing-our-embedded-form/payment-methods-process.md).

# Payment Methods process

## How our FrontStream Embedded Payment Form Handles Payment Methods

Our **FrontStream Embedded Payment Form** handles multiple payment methods by dynamically adjusting the form based on the user’s choice of payment method. Example flow:

1. **Payment Method Selection**:
   * The form allows users to select from different payment methods (credit/debit card, Google Pay, Apple Pay, ACH, etc.).
2. **Show Relevant Fields**:
   * Based on the user’s selection, the embedded form will display the appropriate fields for that payment method.
     * **For credit/debit cards**: Show card number, expiration date, and CVV fields.
     * **For Google Pay/Apple Pay**: Show the respective wallet buttons (which, when clicked, launches the wallet’s payment interface).
     * **For ACH**: Display fields for the user to enter their bank account and routing numbers.
3. **Payment Processing and Surcharging**:
   * The end-user enters payment details, which are secured within the iframe, ensuring that no sensitive information is transmitted to the customer's servers. 
   * Once the user submits the form, the **FrontStream Embedded Payment Form** processes the payment using the selected method.
   * For **Surcharging**, the **FrontStream Embedded Payment Form** will calculate and display any applicable fee before proceeding with payment processing simplifying the surcharging implementation process.
4. **Confirmation**: The customer receives transaction metadata, allowing them to confirm the payment without handling sensitive data directly. 
5. **Receipts**: The purchaser or donor receives a receipt sent to their email detailing the transaction.  


---

# 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/introducing-our-embedded-form/payment-methods-process.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.