XooCode(){

PaymentMethod

PaymentMethod is a schema.org Intangible that also functions as an Enumeration. It is the value of:

It has 8 canonical members:

  • ByBankTransferInAdvance: bank / wire transfer paid before fulfilment.
  • ByInvoice: billed on invoice (net terms).
  • Cash: physical cash.
  • CheckInAdvance: paper check paid before fulfilment.
  • COD: cash on delivery.
  • DirectDebit: pre-authorised debit from a bank account.
  • PaymentMethodCreditCard: credit-card payment.
  • PayPal: PayPal.

Schema.org also defines PaymentCard and PaymentService as more-specific subtypes for card-token flows and third-party payment services.

Full example of schema.org/PaymentMethod json-ld markup

The markup is verified as valid with Rich Results Test from Google.

schema.org/PaymentMethod
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Restaurant",
  "name": "The Dunmore Grill",
  "acceptedPaymentMethod": [
    "https://schema.org/Cash",
    "https://schema.org/PaymentMethodCreditCard",
    "https://schema.org/PayPal"
  ]
}
</script>

Minimal valid version

The smallest markup that still produces a valid PaymentMethod entity. Use it as the floor. Reach for the advanced example above when you want search engines and AI agents to understand more about your content.

schema.org/PaymentMethod (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Restaurant",
  "acceptedPaymentMethod": "https://schema.org/PaymentMethodCreditCard"
}
</script>

Google rich results this unlocks

PaymentMethod is a structural type. It does not produce a rich result on its own.

Its value comes from combining it with a primary type whose markup earns a rich result (Article, Product, Event, and so on). PaymentMethod becomes the trunk that the primary type branches off viamainEntityorbreadcrumb. Include it on every page as the backbone of your markup.

Common PaymentMethod mistakes

Mistakes that pass validation but silently fail to earn rich results or mislead consumers walking the graph. Avoid these and your markup will be ahead of most sites in the wild.

  1. 01

    paymentAccepted text with PaymentMethod URL confusion

    Wrong
    Mixing the legacy paymentAccepted text field with enum-valued acceptedPaymentMethod on the same entity
    Right
    paymentAccepted (LocalBusiness, Text) for human-readable; acceptedPaymentMethod (Offer/Demand, PaymentMethod) for structured

    Both properties exist; they target different slots. Use paymentAccepted for LocalBusiness-level prose and acceptedPaymentMethod for Offer-level structured values.

  2. 02

    CreditCard instead of PaymentMethodCreditCard

    Wrong
    "acceptedPaymentMethod": "https://schema.org/CreditCard"
    Right
    "https://schema.org/PaymentMethodCreditCard"

    Schema.org's credit-card enum member is prefixed 'PaymentMethod'; the plain 'CreditCard' URL does not resolve.

Schema properties in this example

PaymentMethodEnumerationIntangibleByBankTransferInAdvanceByInvoiceCashCheckInAdvanceCODDirectDebitPaymentMethodCreditCardPayPalPaymentCardPaymentServiceacceptedPaymentMethodpaymentMethodappliesToPaymentMethodRestaurantOfferDemandOrder

About the example data

Payment methods accepted at The Dunmore Grill.

Comments

Loading comments...

Leave a comment