From 6c134f2966170e3241a996410e8a3aeec3e0f514 Mon Sep 17 00:00:00 2001 From: sudhirkumar2018 <36911383+sudhirkumar2018@users.noreply.github.com> Date: Mon, 10 Dec 2018 16:48:13 +0530 Subject: [PATCH 1/3] Update README.md Updated ReadMe.md file for chase pay --- README.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/README.md b/README.md index 75eaaa2..54ee968 100644 --- a/README.md +++ b/README.md @@ -79,6 +79,22 @@ Additionally, you can find details and examples of how our API is structured in 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. +## Create a Chase Pay Transaction +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. + +The following information is required in the request: + +- The payment token, +- The expiration date, +- The cryptogram received from the token provider, +- The tokenRequestorName, +- The tokenRequestorId, and +- The tokenRequestorEci. + +When using the SDK to submit Chase Pay transactions, consider the following points: +- TokenRequesterName must be populated with “CHASE_PAY” +- TokenRequestorID must be populated with as provided by Chase Pay services for each transaction during consumer checkout +- TokenRequesterECI must be populated with as provided by Chase Pay services for each transaction during consumer checkout ## Building & Testing the SDK From 3df7d8046bc6541e27982ad0cd553b9a254eb241 Mon Sep 17 00:00:00 2001 From: sudhirkumar2018 <36911383+sudhirkumar2018@users.noreply.github.com> Date: Wed, 12 Dec 2018 20:26:17 +0530 Subject: [PATCH 2/3] Update README.md changed the readme file --- README.md | 21 +++++++++++---------- 1 file changed, 11 insertions(+), 10 deletions(-) diff --git a/README.md b/README.md index 54ee968..034c2ef 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,5 @@ # Authorize.Net Python SDK +# Authorize.Net Python SDK [![Travis CI Status](https://travis-ci.org/AuthorizeNet/sdk-python.svg?branch=master)](https://travis-ci.org/AuthorizeNet/sdk-python) [![Coverage Status](https://coveralls.io/repos/github/AuthorizeNet/sdk-python/badge.svg?branch=master)](https://coveralls.io/github/AuthorizeNet/sdk-python?branch=master) @@ -80,21 +81,21 @@ Additionally, you can find details and examples of how our API is structured in 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. ## Create a Chase Pay Transaction + 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. The following information is required in the request: - -- The payment token, -- The expiration date, -- The cryptogram received from the token provider, -- The tokenRequestorName, -- The tokenRequestorId, and -- The tokenRequestorEci. +- The **payment token**, +- The **expiration date**, +- The **cryptogram** received from the token provider, +- The **tokenRequestorName**, +- The **tokenRequestorId**, and +- The **tokenRequestorEci**. When using the SDK to submit Chase Pay transactions, consider the following points: -- TokenRequesterName must be populated with “CHASE_PAY” -- TokenRequestorID must be populated with as provided by Chase Pay services for each transaction during consumer checkout -- TokenRequesterECI must be populated with as provided by Chase Pay services for each transaction during consumer checkout +- `tokenRequesterName` must be populated with **`”CHASE_PAY”`** +- `tokenRequestorId` must be populated with the **`Token Requestor ID`** provided by Chase Pay services for each transaction during consumer checkout +- `tokenRequesterEci` must be populated with the **`ECI Indicator`** provided by Chase Pay services for each transaction during consumer checkout ## Building & Testing the SDK From b3d903a715f3b62b27d3c3fa4ed3a4b6a24fd5cc Mon Sep 17 00:00:00 2001 From: Gabriel Broadwin Nongsiej Date: Thu, 13 Dec 2018 11:50:22 +0530 Subject: [PATCH 3/3] - Removing repeated heading --- README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/README.md b/README.md index 034c2ef..5848791 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,4 @@ # Authorize.Net Python SDK -# Authorize.Net Python SDK [![Travis CI Status](https://travis-ci.org/AuthorizeNet/sdk-python.svg?branch=master)](https://travis-ci.org/AuthorizeNet/sdk-python) [![Coverage Status](https://coveralls.io/repos/github/AuthorizeNet/sdk-python/badge.svg?branch=master)](https://coveralls.io/github/AuthorizeNet/sdk-python?branch=master) @@ -119,4 +118,4 @@ For additional help in testing your own code, Authorize.Net maintains a [compreh ## License -This repository is distributed under a proprietary license. See the provided [`LICENSE.txt`](/LICENSE.txt) file. \ No newline at end of file +This repository is distributed under a proprietary license. See the provided [`LICENSE.txt`](/LICENSE.txt) file.