Skip to content

Commit 83fd625

Browse files
authored
Merge pull request #153 from nagarikantipavan/ChasePaySDKchanges
chase pay changes
2 parents ef0c8c8 + 15026eb commit 83fd625

1 file changed

Lines changed: 17 additions & 0 deletions

File tree

README.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -81,6 +81,23 @@ Additionally, you can find details and examples of how our API is structured in
8181

8282
The API Reference Guide provides examples of what information is needed for a particular request and how that information would be formatted. Using those examples, you can easily determine what methods would be necessary to include that information in a request using this SDK.
8383

84+
## Create a Chase Pay Transaction
85+
86+
Use this method to authorize and capture a payment using a tokenized credit card number issued by Chase Pay. Chase Pay transactions are only available to merchants using the Paymentech processor.
87+
88+
The following information is required in the request:
89+
- The **payment token**,
90+
- The **expiration date**,
91+
- The **cryptogram** received from the token provider,
92+
- The **tokenRequestorName**,
93+
- The **tokenRequestorId**, and
94+
- The **tokenRequestorEci**.
95+
96+
When using the SDK to submit Chase Pay transactions, consider the following points:
97+
- `tokenRequesterName` must be populated with **`”CHASE_PAY”`**
98+
- `tokenRequestorId` must be populated with the **`Token Requestor ID`** provided by Chase Pay services for each transaction during consumer checkout
99+
- `tokenRequesterEci` must be populated with the **`ECI Indicator`** provided by Chase Pay services for each transaction during consumer checkout
100+
84101

85102
## Building & Testing the SDK
86103
Build the SDK with Maven

0 commit comments

Comments
 (0)