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

# Venmo

> Accept Venmo payments from customers in United States, and check the PSPs that process Venmo through Payrails.

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

Venmo is a digital wallet for customers in the United States. Customers approve the payment in the Venmo app instead of entering card details. Payrails processes Venmo through Braintree.

## How a Venmo payment works

Venmo is an app-based payment method. The customer approves in Venmo before you call Payrails:

1. The customer selects Venmo at checkout.
2. The Braintree client SDK sends the customer to the Venmo app on mobile, or shows a QR code to scan on desktop.
3. The customer approves the payment in the Venmo app.
4. The Braintree client SDK returns a single-use payment method nonce to your checkout.
5. You send the nonce to Payrails in the authorize request, and Payrails charges it through Braintree.

There's no redirect: Payrails returns the result of the Braintree transaction in the authorize response.

## Supported currencies and countries

Venmo supports USD (United States dollar) as its presentment currency. Payrails sends the currency you provide to Braintree without checking it first.

Venmo is available to customers based in:

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

  <tbody>
    <tr><td>**North America**</td><td>🇺🇸 United States</td></tr>
  </tbody>
</table>

## Integrate Venmo

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

> [card]
>
> Braintree logo
>
> BraintreeVenmo via Braintree
>
> [Open](https://docs.payrails.com/docs/integrations/payment-methods/venmo/braintree.md)

## Check PSPs

<table>
  <thead>
    <tr><th>Workflow</th><th>[Braintree](https://docs.payrails.com/docs/integrations/payment-methods/venmo/braintree.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 Venmo

* **Payrails SDK:** the [Web SDK](https://docs.payrails.com/docs/sdks/web.md) shows Venmo 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 `venmo` 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

- [Venmo via Braintree](https://docs.payrails.com/docs/integrations/payment-methods/venmo/braintree.md)
- [Create a new Ruleset](https://docs.payrails.com/reference/createruleset.md)
- [Update a Ruleset](https://docs.payrails.com/reference/updateruleset.md)


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