.svg)
acceptedPaymentMethod
acceptedPaymentMethod · Optional
Appears in
What is it?
acceptedPaymentMethod declares the payment methods an organization accepts for transactions. It answers the question "how can I pay?" at the markup level, making payment capabilities machine-readable rather than buried in checkout flows or FAQ pages.
The field accepts PaymentMethod values, LoanOrCredit values, or plain Text strings. Schema.org's PaymentMethod type has a set of enumerated values covering common payment options, from credit cards to bank transfers.
Why this matters for AEO
Payment method availability is a concrete purchasing consideration that AI engines surface in commercial queries. When a user asks "does this company accept PayPal?" or "which vendors accept purchase orders?", an AI assistant that can read acceptedPaymentMethod from structured data gives a direct answer rather than directing the user to search through a checkout page.
For B2B organizations where invoicing, net terms, or wire transfers are standard, making payment method information structured and crawlable improves the accuracy of AI-generated vendor comparison answers. For consumer businesses, it addresses a common friction point before purchase.
What the specs say
Schema.org:acceptedPaymentMethod expects a PaymentMethod, LoanOrCredit, or Text value. The payment method(s) that are accepted in general by an organization, or for some specific demand or offer. [Source: https://schema.org/acceptedPaymentMethod]
Google: Not mentioned in Google's structured data documentation for Organization. [Source: https://developers.google.com/search/docs/appearance/structured-data/organization]
Schema.org PaymentMethod values
Schema.org defines enumerated values for common payment methods. Use these as the @id value on a PaymentMethod node:
- Cash —
https://schema.org/Cash - Credit card —
https://schema.org/CreditCard - Debit card —
https://schema.org/DebitCard - Check —
https://schema.org/ByCheck - Bank transfer —
https://schema.org/ByBankTransferInAdvance - Invoice —
https://schema.org/Invoice - PayPal —
https://schema.org/PayPal
For payment methods not covered by the enumeration, use a descriptive text string.
How to find your value
Check your checkout flow, pricing page, and billing FAQ for the complete list. For B2B companies, consult your accounts receivable team to capture all accepted methods including wire transfers, ACH, and purchase orders.
Format and code
Text strings (simple approach)
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Shopify",
"acceptedPaymentMethod": ["Credit Card", "PayPal", "Apple Pay", "Google Pay"]
}
Enumerated PaymentMethod values
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Square",
"acceptedPaymentMethod": [
{
"@type": "PaymentMethod",
"@id": "https://schema.org/CreditCard"
},
{
"@type": "PaymentMethod",
"@id": "https://schema.org/DebitCard"
},
{
"@type": "PaymentMethod",
"@id": "https://schema.org/Cash"
}
]
}
Mixed structured and text values
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Salesforce",
"acceptedPaymentMethod": [
{
"@type": "PaymentMethod",
"@id": "https://schema.org/CreditCard"
},
{
"@type": "PaymentMethod",
"@id": "https://schema.org/Invoice"
},
"Purchase Order",
"Wire Transfer",
"ACH"
]
}
LoanOrCredit for financing options
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Apple",
"acceptedPaymentMethod": [
{
"@type": "LoanOrCredit",
"name": "Apple Card Monthly Installments",
"loanType": "Installment"
},
{
"@type": "PaymentMethod",
"@id": "https://schema.org/CreditCard"
}
]
}
Webflow implementation
Static pages
Add acceptedPaymentMethod to the Organization JSON-LD block in Page Settings > Custom Code. For organizations with a fixed payment method list, hardcode the array. Text strings are the simplest approach for most organizations.
CMS template pages
For marketplace or directory sites where different vendors accept different payments, store accepted payment methods as a multi-select CMS field. In the CMS template, inject the values as a JSON array in the custom code embed.
In Schema HQ
acceptedPaymentMethod supports in the Organization editor. Enter payment methods as text values. Schema HQ serializes them into the correct array format in the JSON-LD output.
Real examples
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Etsy",
"url": "https://www.etsy.com",
"acceptedPaymentMethod": [
"Credit Card",
"Debit Card",
"PayPal",
"Apple Pay",
"Google Pay",
"Etsy Gift Card"
]
}
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Zendesk",
"url": "https://www.zendesk.com",
"acceptedPaymentMethod": [
"Credit Card",
"Invoice",
"Purchase Order",
"Wire Transfer",
"ACH"
]
}
Related fields
FAQ
Should I use enumerated PaymentMethod values or text strings?
Enumerated values from schema.org's PaymentMethod type provide better semantic precision and interoperability. Text strings are simpler and work for payment methods not covered by the enumeration (like ACH or purchase orders). A mixed approach, using enumerated values where they exist and text for the rest, is valid.
Can acceptedPaymentMethod appear on an Offer instead of an Organization?
Yes. acceptedPaymentMethod also applies to individual Offer, Demand, and some other types. Using it at the Organization level captures your default payment policy. Using it on a specific Offer lets you specify different payment options for different products or services.
Is it valid to list Apple Pay and Google Pay as payment methods?
Yes, as text strings. Schema.org's enumerated PaymentMethod values do not include Apple Pay or Google Pay specifically. Use descriptive text strings for these. Validators accept text values alongside structured PaymentMethod nodes.
