# JPMC-PDP Documentation from https://developer.payments.jpmorgan.com

# Resources

## Principal Protection (PPRO)

Principal Protection is a service that protects cross-border USD wire payments from variable intermediary and correspondent fees as the payment passes through the payment chain. For a fixed fee, this service ensures that the full value of the payment reaches the beneficiary without any fee deductions, with the remitter covering these fees.

## Supported Statuses

Same-currency wire payments support the following statuses:

- Status:  Accepted | Sub-status: Accepted

- Status:  Completed | Sub-status: Completed by JPM

- Status:  Rejected | Sub-status: Rejected

- Status:  Returned | Sub-status: Returned

For a full list of status response and error codes, see [status responses and error codes](/api/treasury/global-payments/global-payments-2/error-codes).

## Transfer limits

The following sections show the transfer limits for wire transactions by region.

### North America (NA)

- Fed or CHIPS: $9.9 billion

- Book transfer: $25 billion

## Cutoff times

A cutoff time identifies the deadline to submit a payment so that it settles on the corresponding settlement date.

The following sections show regional supported cutoff time or times for a wire payment.

### North America (NA)

 
**United States cutoff times**

| Electronic Initiation | CHIPS | Fedwire | Book Transfer | Description | 
| --- | --- | --- | --- | --- | 
| Straight-Through | 17:30 | 18:15 | 19:15 | Debit to a client's account, initiated though an electronic banking system or SWIFT, and processed straight through without operator intervention. | 
| Operator Repair | 17:00 | 17:30 | 18:45 | Debit to a client's account, initiated through an electronic banking system and that required operator's intervention. | 
| Drawdown In | N/A | 17:30 | 19:15 | Debit to client's account in response to a Fedwire drawdown request. | 
| Fed Drawdown Out | N/A | 17:30 | N/A | Fedwire drawdown request, initiated electronically, to draw funds into a J.P. Morgan account. | 
| Fed Settlement | N/A | 18:00 | N/A | Bank-to-bank end of day settlement by an FI with the Federal Reserve Bank (Fed Type code 16 wire transaction). | 
| Federal Tax Payments | N/A | 15:00 | N/A | Execution of a Fedwire in settlement of an IRS tax payment. | 
| Foreign Central Bank Payments | N/A | 16:00 | N/A | A transfer to a foreign central bank with an account at the Federal Reserve Bank (Fed Type code 15 wire transaction) | 

> All times in New York (Standard Time).
> 

 
**Wire cutoff times**

|  | Access Next Gen | PaySource & H2H | SWIFT FIN | 
| --- | --- | --- | --- | 
| USD | 4:30 PM ET | 4:30 PM ET | 4:30 PM ET | 

> All times in ET.
> 

## Duplicate logic

A wire payment is irrevocable. If the same payment is sent twice, the status of the original payment is returned with the original `paymentId`*. *To confirm the status of any transaction, [get the status of a wire payment.](/docs/treasury/global-payments/capabilities/global-payments-2/wire/how-to/get-wire-request-status)

## Duplicate transactions

The Global Payments API supports [idempotent calls](/api/treasury/global-payments/overview#idempotency-logic), which are useful when initiating a payment, creating a client, making a change, or retrying a failed request due to issues like network problems.

If a wire payment shares the same `endToEndId` as another wire payment within a specified timeframe, the Global Payments API considers it duplicative.

The following table contains each country's specified timeframe:

 
**Duplicate transaction timeframes for Wire**

| Country | Timeframe | 
| --- | --- | 
| United States | 60 days | 

## Tax payments (SWIFT)

When sending FED payments to the Treasury Department solely for settling tax payments, you must adhere to specific requirements:

- The beneficiary's customer account, along with the institution and remittance information you provide, must adhere to a specific model.

- Cut-off times for tax payments is 15:00 Eastern Time. Payments received after this time are processed on a reasonable-effort basis.

### Account with institution

**Single business tax payer (SBT):**

- Line 1 - //FW091036164

- Line 2 - US TREASURY SINGLE TAXPAYORS

- Line 3 - MINNEAPOLIS MN US

**Bulk provider taxpayer (BPT)**

- Line 1 - //FW091036177

- Line 2 - FRBM/BK OF AMERICA

- Line 3 - MINNEAPOLIS MN US

**Sample:**

`:57D//FW091036164`

`US TREASURY SINGLE TAXPAYORS`

`MINNEAPOLIS MN US`

### Beneficiary customer

- Line 1 - /20092900

- Line 2 - IRS

- Line 3 - MINNEAPOLIS MN US

**Sample:**

`:59:/20092900`

`IRS`MINNEAPOLIS MN US`

### Remittance information

The items listed below should be arranged in sequence, beginning with the first line of Field 70 and continuing onto additional lines as necessary. Each piece of information must be separated by a colon and end with one.

- Nine-digit tax payer ID number

- Taxpayer name control (first 4 letters of your business name)

- Taxpayer name (up to 35 characters)

- Tax type (5 digits)

- Tax year (2 digits)

- Tax month (2 digits, use a preceding zero for single-digit months)

**Sample:**

`:70:1BBB56789:JONE:JONESCOMPANY INC:
 72005:17:03:`

## Sanctions screening

J.P. Morgan screens the remittance information and ultimate debtor information to comply with United States OFAC regulations, applicable non-U.S. sanctions, and national and international anti-terrorism laws.