Note that there are some explanatory texts on larger screens.

plurals
  1. POHandling Data for Credit Card Transaction with Payment Form Hosted on Website
    primarykey
    data
    text
    <p>While developing a credit card transaction page for a website to transmit data to the payment gateway, I notice that many input options are available. The return response from the payment gateway also contains a myriad of data.</p> <p>Listed below are some <strong>input fields</strong> which, I believe, are captured on most payment gateways:</p> <ul> <li>customer's address</li> <li>customer id</li> <li>customer's IP address</li> <li>description</li> <li>email</li> <li>first name and last name</li> <li>invoice number and PO number</li> <li>tax and tax exempt status</li> <li>transaction id</li> </ul> <p>Listed below are some <strong>response fields</strong> which, I believe, would generally be returned to the website:</p> <ul> <li>overall response (accept, reject, error, hold)</li> <li>specific responses (such as address verification, card CCV verification, etc)</li> <li>specific description of response</li> <li>hash (unique to merchant account)</li> <li>data from the input above</li> </ul> <p>I would like to find out:</p> <ol> <li>Which data would you process internally without sending to the gateway?</li> <li>Which data would you route through the gateway before processing?</li> <li>Which responses would you use for further processing?</li> <li>Which responses would you store for future reference, and why?</li> </ol> <p>I believe this decision making process is what web developers would normally encounter when they set an e-commerce application. Would anyone like to share his/her knowledge?</p> <p>To start the ball rolling, let me attempt</p> <ol> <li>Which data would you process internally without sending to the gateway?</li> </ol> <p><strong>email</strong> - I would notify customers of a successful transaction by emailing directly from my web application. The payment gateway provider does not need to know my customers' detail.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload