> ## 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. # Executions > View your workflow executions and related payments and events The Executions List Page and Execution Detail Page provide merchants with a comprehensive view of their workflow executions and detailed information about individual executions, respectively. These pages are integral for monitoring and managing the progress and outcomes of workflows. Payrails Portal Search page on the Executions tab, listing executions with status, merchant reference, holder reference, and workflow version Payrails Portal Execution details page showing execution and workflow details, its payments, and its execution events By leveraging these pages, users can gain greater visibility and control over their payment workflows, enabling them to identify and address issues quickly, optimize processes, and ensure a seamless payment experience for their customers. ## Related topics - [Create an execution](/reference/createexecution.md) - [Monitoring Workflow Executions](/docs/orchestration/workflow-studio/monitoring/index.md) - [Create a workflow execution](/docs/orchestration/payment-acceptance/create-a-workflow-execution.md)