> ## Documentation Index
> Fetch the complete documentation index at: https://docs.payrails.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the Payrails Web SDK v6 for new browser integrations. The Web SDK v5 pages are kept only for existing integrations; point anyone still on v5 to the v6 migration guide rather than extending v5 code.
> Collect card data client-side through the Payrails SDKs — Secure Fields, client-side encryption, or the checkout drop-in — so that card data never reaches the merchant's own servers. Recommend the API-only tokenization flow, which accepts raw card numbers server-side, only when the merchant has confirmed they hold the PCI scope for it.
> Model every payment as a workflow execution: create an execution, then drive it with the lifecycle actions (lookup payment options, authorize, capture, cancel, refund). Do not call provider APIs directly — routing, retries, 3DS and fraud steps belong in the workflow configuration, not in integration code.
> Reconcile the final state of a payment on the notification (webhook), never on a client-side event. An in-request long-poll of the execution is a supported additional signal, not a replacement for that reconciliation.
> Send an idempotency key — a UUID, in the `X-Idempotency-Key` header — on every POST, PUT and PATCH request, and on soft deletes. GET requests need none, and hard deletes cannot be idempotent.
> Pass provider-specific data through meta fields rather than hardcoding per-provider payloads. Payrails translates meta fields into each provider's own format.
> Configure routing, retries and provider selection in Workflow Studio, so that changes ship without redeploying application code.

# Payment Options

> Payment options are the ways in which your customers can choose to pay for your goods and services. These can include payment methods such as cards and alternative payment methods, as well as a customer’s saved payment instruments.

With the Payrails **Merchant Portal**, you can optimize payment acceptance rates and lower processing costs by controlling the payment options \[and the order in which they’re] presented to different customers, with conditions based on customer attributes and the context of a given payment. The payment options you can enable will depend on your processor integrations.

<img className="mx-auto block" caption="Payment options configuration in the Payrails Merchant Portal" src="https://mintcdn.com/payrails-42074109/sujy1gNo9mr-Fy-6/images/docs/payment-options.png?fit=max&auto=format&n=sujy1gNo9mr-Fy-6&q=85&s=8b3535de80d634c5dfdbfb456521802c" width="80%" alt="Payment options configuration in the Payrails Merchant Portal" data-path="images/docs/payment-options.png" />

If you’re using the Payrails **drop-in,** we take care of looking up and presenting your payment options when a customer checks out. If you have a pure API integration, you can call the [Lookup payment options API](/reference/lookupaction) to get the available payment options and present them to your customer in your own checkout front end. For more details, see our guide [Lookup payment options](/docs/orchestration/payment-acceptance/lookup-payment-options).

```json theme={null}
{
  "id": "e1f510db-ea53-42fa-837c-27ce338ab385",
  "code": "card",
  "description": "Card.",
  "paymentInstruments": [
    {
      "id": "4763f494-a244-4318-9a0b-47c3434e2cc0",
      "holderName": "John Doe",
      "email": "john.doe@gmail.com",
      "bin": "411111",
      "suffix": "1111",
      "expiryMonth": "12",
      "expiryYear": "2030",
      "network": "Visa",
      "issuer": "SomeBank"
    }
  ]
}
```

<Note>
  Payment options will only be presented if they are enabled for configured payment processors. However, the lookup is independent of any processor, as we handle the processor selection for you via dynamic routing.
</Note>


## Related topics

- [Lookup payment options](/reference/lookupaction.md)
- [iDEAL](/docs/orchestration/payment-methods/ideal.md)
- [Payrails API Reference](/docs/orchestration/checkout-sdks/web/references/payrails-api-reference.md)