You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+17Lines changed: 17 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,6 +64,23 @@ Additionally, you can find details and examples of how our API is structured in
64
64
65
65
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.
66
66
67
+
## Create a Chase Pay Transaction
68
+
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.
69
+
70
+
The following information is required in the request:
71
+
72
+
- The payment token,
73
+
- The expiration date,
74
+
- The cryptogram received from the token provider,
75
+
- The tokenRequestorName,
76
+
- The tokenRequestorId, and
77
+
- The tokenRequestorEci.
78
+
79
+
When using the SDK to submit Chase Pay transactions, consider the following points:
80
+
- TokenRequesterName must be populated with “CHASE_PAY”
81
+
- TokenRequestorID must be populated with <tokenRequestorID> as provided by Chase Pay services for each transaction during consumer checkout
82
+
- TokenRequesterECI must be populated with <eciIndicator> as provided by Chase Pay services for each transaction during consumer checkout
0 commit comments