Resources
Response types
Push to Card supports multiple response types, including PENDING, REJECTED, WAREHOUSED, COMPLETED, and RETURNED. The following table explains these response types in more detail:
Status |
Description |
|---|---|
|
The request was initiated successfully, and is being processed by J.P. Morgan. The status will remain as PENDING until an event occurs to change the status. |
|
The request failed J.P. Morgan controls (e.g., sanctions, funds control, qualification), or the request was rejected by the Clearing House due to recipient account issues, incorrect instruction, or an unverified recipient. |
|
The request was successfully received. The request will be processed on the requested execution date. |
|
The funds were successfully credited to the recipient’s payment method. |
|
The funds were successfully credited to the client’s account. This is not a regular payment status. |
Back and future dated transactions
Push to Card supports back and futured dated transaction processing. Back-dated transactions are supported up to one calendar day behind (T-1) and future-dated transactions are supported up to five 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 presents a great opportunity for 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.
Purpose codes
Purpose codes are issued by a market’s Clearing house and identifies the purpose of a transaction. The following table lists supported purpose code values for Push to Card Payments.
Purpose code |
Description |
|---|---|
|
Account management |
|
Transaction is the payment of allowance |
|
Settlement of annuity |
|
Unemployment disability benefit |
|
Business expenses |
|
Bonus payment |
|
Bus transport related business |
|
Cash management transfer |
|
Payment of cable TV bill |
|
Government institute issued related to cash compensation, helplessness, and disability |
|
Credit card payment |
|
Payment of credit card bill |
|
Payment for charity reasons |
|
Collection payment |
|
Commercial payment |
|
Commission |
|
Compensation relating to interest loss/value date adjustment and can include fees |
|
Payment of copyright |
|
Related to a debit card payment |
|
Payment of a deposit |
|
Payment of dividend |
|
Payment of study / tuition fees |
|
Payment of electricity bill |
|
Energies |
|
General fees |
|
Payment for ferry related business |
|
Foreign exchange |
|
Payment of gas bill |
|
Compensation to unemployed persons during insolvency procedures |
|
Government payment |
|
Health insurance |
|
Reimbursement of credit card payment |
|
Reimbursement of debit card payment |
|
Payment of car insurance premium |
|
Transaction is related to the payment of an insurance claim |
|
Installment |
|
Insurance premium |
|
Payment of mutual funds, investment products and shares |
|
Intra company payment |
|
Interest |
|
Income tax |
|
Investment |
|
Labor insurance |
|
License fee |
|
Life insurance |
|
Loan |
|
Medical services |
|
Mobile P2B payment |
|
Mobile P2P payment |
|
Mobile top up |
|
Not otherwise specified |
|
Other |
|
Transaction is related to a payment of other telecom related bill |
|
Payroll |
|
Contribution to pension fund |
|
Pension payment |
|
Payment of telephone bill |
|
Property insurance |
|
Transaction is for general rental/lease |
|
The payment of rent |
|
Payment for railway transport related business |
|
Royalties |
|
Salary payment |
|
Payment to savings / retirement account |
|
Securities |
|
Social security benefit |
|
Study |
|
Subscription |
|
Supplier payment |
|
Refund of a tax payment or obligation |
|
Tax payment |
|
Transaction is related to a payment of telecommunications related bill |
|
Trade services operation |
|
Treasury payment |
|
Payment for travel |
|
Utility bill payment |
|
Value added tax payment |
|
With holding |
|
Payment of water bill |
Payment Limits
Push to Card Payments are subject to maximum payment amounts, which vary depending on the use case. The card network that mandates these thresholds periodically reviews these limits in response to market demands and conditions.
Use Case |
Payment limit (per transaction) |
|---|---|
General Funds Disbursement |
$125,000 |
Money Transfer (TP3) |
$50,000 |
Duplicate logic
Push to Card payments are irrevocable. If the same transaction is sent twice, the status of the original transaction is returned. To confirm the status of any transaction, retrieve the status of a Push to Card request.
How we handle duplicate transactions
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 Push to Card transaction is deemed to be a duplicate by the Global Payments API if the original transaction has the same endToEndId and alternateAccountIdentifier (programId).
If two transactions are sent with the same preceding parameter IDs within 30 days, the transaction is flagged as duplicate, and the status of the original transaction is returned.
Sanctions screening
J.P. Morgan screens the payment information to comply with U.S. OFAC regulations, applicable non-U.S. sanctions, and national and international anti-terrorism laws.