> For the complete documentation index, see [llms.txt](https://docs.feathery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feathery.io/platform/build-forms/elements/fields/payment-method.md).
# Payment Method
The Payment Method field, backed by Stripe, allows users to securely enter a PCI-compliant credit card number.
Once the [Stripe integration](https://www.feathery.io/integrations/stripe) is activated and set up, the Payment Method field will become available to use for capturing payment information as part of a payment flow. Presently, only credit cards are supported.
This payment method field may be dragged anywhere onto your form and is the only way to enter payment/card information in your form to be passed securely to Stripe. The payment method field collects the card number, CVC, expiration month/year and postal code. It supports standard styling.
Once your end user fills the field and submits the step, the payment method will be automatically saved into the customer record in Stripe.
Payment Method in the Feathery designer
### For Developers
The Feathery SDK and API reference payment method fields with `type` equal to `payment_method`. The submitted value is `json`. The value of this field is read-only and not settable via the SDK.
Example value:
```
{
card_data: {
brand: "discover",
last4: "1117",
country: "US",
exp_year: 2029
exp_month: 9
},
stripe_payment_method_id: "pm_aD45hG60f3twY"
}
```
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.feathery.io/platform/build-forms/elements/fields/payment-method.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
