Skip to main content
Beta version available

Discover the Global Payments 2 API, now available in beta!

Resources

Payment/creditor options

Payments via Push to Wallet can be sent to a beneficiary’s PayPal or Venmo wallet using the beneficiary’s email address or mobile phone number that is registered to their account.

The beneficiary's email address or mobile number must be registered with PayPal or Venmo before payments can be disbursed to these wallets.

Tip

Payments sent to invalid, unverified or unregistered email address or phone number will be rejected.

Purpose codes

PayPal/Venmo requires a purpose code to be included in every payout request.  The following is a list of valid purpose codes.

Purpose code values

Code value

GOODS

SERVICES

NON_GOODS_OR_SERVICES

REBATES

CASHBACK

AWARDS

DISCOUNTS

DONATIONS
PRIZES

Duplicate Logic

The Global Payments API supports the ability for idempotent calls. This is useful in various scenarios, such as initiating payments, creating a client, making changes, or attempting to retry a failed request (for instance, due to network issues).

A transaction is deemed to be a duplicate by the Global Payments API if the second transaction has the same endToEndId and debtorAccountId as a previous transaction within 30 days. In this case, JPM will send a 202 response with the status of the original transaction and the second transaction will not be processed.

Do not send the same transaction more than once unless you have confirmed the initial transaction was rejected. To confirm the status of any transaction, retrieve the status of a Disbursements with Zelle® request.

Back-dated and future-dated Transactions

Push to Wallet supports back and future dated transaction processing. Back-dated transactions are supported up to one calendar day behind (T-1) and future-dated transactions are supported up to 5 calendar days ahead of time (T+5). 

Future-dated transactions will be marked as WAREHOUSED up until the requested date then subsequently released for continued processing. This allows clients to efficiently manage their cash flow and enables clients who currently follow a batch processing model to stagger their payment processing throughout multiple days.

Clients subscribing to callbacks/webhooks or using the GET request to the /payments/status endpoint can expect to receive a WAREHOUSED status.

Sanctions screening

J.P. Morgan screens client payment information to comply with U.S. Office of Foreign Assets Control (OFAC) regulations, applicable non-U.S. sanctions, and national and international anti-terrorism laws.