> ## 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.

# Analytics & Reporting

> Configure data ingestion for each supported payment provider and data source so you can start using analytics and reporting in Payrails.

To start using analytics and reporting, add each payment provider you use as a data source.

Connect your data sources

Add your providers in the Portal to power analytics, reporting and fee monitoring.

[Open](https://docs.payrails.com/docs/integrations/data-sources)

Upload files

Send your own files through the API or the Portal to extend the data set.

[Open](https://docs.payrails.com/docs/analytics-and-reporting/upload-files.md)


## Related topics

- [Integrations](https://docs.payrails.com/docs/integrations.md)
- [Unified Analytics](https://docs.payrails.com/docs/analytics-and-reporting/unified-analytics.md)
- [Tap](https://docs.payrails.com/docs/integrations/data-sources/tap.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.