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

# SafetyPay

> Accept SafetyPay payments from customers in Peru, including how pending payments resolve after the customer returns.

<picture noZoom>
  ![SafetyPay logo](https://assets.payrails.io/img/logos/safetypay/logo-full-bleed.svg)
</picture>

SafetyPay is a payment method in Latin America that lets customers pay without a card. Payrails processes SafetyPay for customers in Peru through Worldpay.

## How a SafetyPay payment works

SafetyPay is a redirect payment method that can complete after the customer returns:

1. The customer selects SafetyPay at checkout.
2. Payrails returns a redirect URL from Worldpay, and the customer goes to SafetyPay.
3. The customer confirms the payment with SafetyPay.
4. SafetyPay sends the customer back to your `returnInfo` URL.
5. Payrails receives the final result from Worldpay and updates the payment.

The customer can return before the money arrives. In that case the payment stays pending until Worldpay sends the final status by webhook. Payrails captures SafetyPay payments immediately, so a successful payment is final.

## Supported currencies and countries

Payrails sends the currency and billing country you provide to Worldpay without checking them first. Worldpay rejects a pairing outside SafetyPay coverage.

SafetyPay is available to customers based in:

<table>
  <thead>
    <tr><th>Regions</th><th>Countries</th></tr>
  </thead>

  <tbody>
    <tr><td>**Latin America**</td><td>🇵🇪 Peru</td></tr>
  </tbody>
</table>

## Integrate SafetyPay

Choose the PSP that processes SafetyPay for you. The guide covers the PSP-side setup, the Payrails configuration and the request fields that PSP requires.

> [card]
>
> Worldpay logo
>
> WorldpaySafetyPay via Worldpay
>
> [Open](https://docs.payrails.com/docs/integrations/payment-methods/safetypay/worldpay.md)

## Check PSPs

<table>
  <thead>
    <tr><th>Workflow</th><th>[Worldpay](https://docs.payrails.com/docs/integrations/payment-methods/safetypay/worldpay.md)</th></tr>
  </thead>

  <tbody>
    <tr><td>Payrails SDK</td><td>✔</td></tr>
    <tr><td>Payrails API</td><td>✔</td></tr>
    <tr><td>[Delayed / Manual Capture](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-and-cancel-modes.md#capture-mode)</td><td>✖</td></tr>
    <tr><td>[Instant Capture](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-and-cancel-modes.md#capture-mode)</td><td>✔</td></tr>
    <tr><td>[Cancel / Void](https://docs.payrails.com/docs/orchestration/payment-acceptance/cancel-a-payment.md)</td><td>✖</td></tr>
    <tr><td>[Refund / Reverse](https://docs.payrails.com/docs/orchestration/payment-acceptance/refund-a-payment.md)</td><td>✔</td></tr>
    <tr><td>[Save Instruments](https://docs.payrails.com/docs/resources/manage-instruments.md)</td><td>✖</td></tr>
    <tr><td>[Merchant Initiated Transaction (MIT)](https://docs.payrails.com/docs/resources/payments/authorization-flags.md)</td><td>✖</td></tr>
  </tbody>
</table>

## Ways to integrate SafetyPay

* **Payrails SDK:** the [Web SDK](https://docs.payrails.com/docs/sdks/web.md) shows SafetyPay when your workflow returns it as a payment option.
* **Payrails API:** call [lookup payment options](https://docs.payrails.com/docs/orchestration/payment-acceptance/lookup-payment-options.md), then authorize with `safetyPay` as the `paymentMethodCode`. The PSP guide lists the `meta` fields that PSP requires.

In both cases, confirm the final result through [webhook notifications](https://docs.payrails.com/docs/orchestration/payment-acceptance/receive-notifications.md) or the execution status.


## Related topics

- [SafetyPay via Worldpay](https://docs.payrails.com/docs/integrations/payment-methods/safetypay/worldpay.md)
- [Worldpay](https://docs.payrails.com/docs/integrations/payment-providers/worldpay.md)
- [Payment Instruments and Tokens](https://docs.payrails.com/docs/resources/manage-instruments.md)


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