<p>U.S. Bank downloads and stores cookies on your device when you visit our website. We use these cookies to better understand and improve your browsing experience by identifying most visited pages, personalizing content, and measuring site performance.</p>


Essential cookies enable core functionality such as page navigation and access to secure areas. The website cannot function properly without these cookies; they can only be disabled by changing your browser preferences.

Performance cookies help us to improve our website by collecting and reporting information on its usage (for example, which of our pages are most frequently visited).

Cookie settings

Accounts

Corporate cards

Institutional

Lending

Payments & collections

Transportation

All APIs

API products

Solution Areas

Product Suites

Solutions

Dashboard

Resources and guides

Developers

Support tickets

Contact us

Support

### Process claim payments.
A claims manager at a nationally known insurance firm issues many claim payments via ACH every year. The firm’s enterprise resource planning (ERP) system needs to follow the new NACHA rule that requires deposit account information to be secure when stored electronically. The Payee Token+ API enables the firm’s ERP system to tokenize claimants’ (payees’) deposit account information to follow the new NACHA rule. The claims manager can originate the claim payments via ACH simply by rendering the claimants’ tokens to U.S. Bank to process the claim payments.
 ### Eliminate manual disbursements.
An administrator at a university manages periodic scholarship disbursements to several qualified students each semester. The university's ERP system, which is used to manage scholarship disbursements, requires sensitive ACH account information for each student to be entered manually every semester. Each student must be set up as a payee, which can take up to four business days to validate the micro deposits. In using the Payee Token+ API, the ERP system can now tokenize and validate the sensitive ACH payment account information for each student, allowing the administrator to make scholarship disbursements to several students by selecting their respective ACH tokens.
### Mitigate data storage risk.
A manager of the checkout platform for a large e-commerce company is looking for a solution to lower data risks associated with the many retail customers who store their credit card information with the company. With the Payee Token+ API, the e-commerce company can manage and reduce the data risks associated with storing customer credit card information by tokenizing and securing data at the U.S. Bank PCI-compliant enclave.

Example use cases

- Account details validation is limited to validating account numbers and respective routing numbers.
- Account details validation is an optional service. Opting in is required prior to receiving the service.
- The scope of Payee Token+ is limited to managing tokens only. Your application maintains the entity (payee) name and its respective token relationship.

Restrictions

<p>Reduce data risk on your application by tokenizing, validating and storing your payee's account details, card numbers and other sensitive information in a highly secure enclave.</p>


Payee Token+

The Payee Token+ API enables your application to tokenize and validate sensitive payee data (PII and PCI data) for various payment rails like *Zelle*®, ACH, RTP®, wires, checks and card information. With your application providing the payee details to Payee Token+, the payee data is tokenized and stored, and your application receives a payee token in return. If opting for the account validation service, the account details such as the account number and routing number are validated for authenticity prior to returning a payee token. This helps reduce the storage risk of fraudulent or erroneous payee details.


Overview

### Create a payee token.
- Create a payee token for the given sensitive account information of the payee.
- Support account information for the following payment rails:
    - ***Zelle*** – includes email address and phone number
    - ACH and RTP – includes account number and routing number
    - Check details – includes payee name and address
    - Domestic wires – includes account number, routing number and corresponding bank details
    - International wires – includes IBAN, BIC / SWIFT code and intermediary bank details
    - Card information – includes 16-digit PAN number and expiry date
- Check for duplicate tokens. Returns existing token if the same account information is passed in the request.
- **Optional value-added account validation service:** Opt in to validate the authenticity of the account information such as account number and routing number of the payee before creating the respective payee token.
- Evaluate the Payee Token+ API features in a sandbox environment by adding it to a project.

### Retrieve payee details.
- Retrieve details of the payee token by passing in the associated token.
- Mitigate data risks and reduce costs associated with storing sensitive payee information.

### Delete a payee token.
- Delete a payee token by passing in associated payee token.

### Validate a payee token.
- Verify if a token is active by passing in the associated payee token.


Features

![Payee Token+ workflow](/content/dam/developer-portal-solutions/en-us/usbank/media/images/products/payee-token/payee-token-workflow.jpg)

Workflow

Alliance Offers

Data as a Service

Invitation to Apply

Bank Holidays

Card Activation

Card Controls

Challenge-Widget

Commercial Credit Cards

Commercial Statements

Credit Card Account Details

Credit Card Accounts Overview

Credit Card Alerts

Credit Card Application Status

Credit Card APRs

Credit Card Balance Transfers

Credit Card Disputes

Credit Card Payments

Credit Card Qualified Offers

Credit Card Statements

Credit Card Transactions

Data Sharing for Marketing Purposes

Digital Wallets

Make a Payment - Coming Soon

Rewards Accelerator

Rewards Automatic Redemption

Rewards: Balance Summary

Rewards: Dashboard

Rewards Redemption Accounts

Rewards Redemptions

Rewards Transactions: Earned and Redeemed

Travel Notifications

User Profile

3DSecure2

CheckoutJs

Commerce SDK

Converge

Disputes Management

Dynamic Currency Conversion

eBoarding

Elavon Cloud Payments Interface

Elavon Payment Gateway

Fusebox

Hosted Payment Page

In Person Payments on Opayo

Leads

Lightbox payment modal

Online Payments on Opayo

Opayo

Opayo Direct

Opayo Forms

Opayo Reporting API

Opayo Server

Opayo Shared API

Payment Method Gateway

Payments Core 365

Simplify

viaconex

XML API

Card as a Service API

Core Banking API

Money Movement API

Reference API

Access Online Transactions

Account Transfers

Account Validation

ACH Originations

Avvance Connect

Avvance Express

Avvance Flex

Bank Information

Card as a Service

Check Payables

Corporate Account Information

Corporate Account Information 3LO

Corporate Credit Cards

Corporate Onboarding

Corporate Statements

Custody

Data Toolbox

Data Toolbox - Accounts

Data Toolbox - Documents

Data Toolbox - Transactions

Debit Card Phone Number Lookup

Disbursements via Zelle®

U.S. Bank Flexible Capital Platform

Freight Payment Customer Profiles

Freight Payment Transactions

Incoming Webhooks

Instant payments

Investment Accounting

PaySmart

Payee Choice

Personal Loans

Positive Pay

Push to Card

Receivables

RTP® - Real-Time Payments

Tokenized Payments

Treasury Builder

U.S. Bank FBO Account

Virtual Account Reporting

Virtual Card Payments

Voyager Accounts

Voyager Cards

Voyager Drivers

Voyager Transactions

Voyager Vehicles

Wire Transfers

Getting started

Security guide

API reference

Release notes

Postman collection

Overview

Features

Workflow

PREVIOUS VERSIONS

PRODUCT DOCUMENTS

Example use cases

Restrictions