search

mozvat / WSPAPIPrototype

Web Services 2.0 prototype work.
1 stars 2 forks source link

Credit Sale - required properties #6

Open mozvat opened 11 years ago

mozvat commented 11 years ago

Here is what is minimally required for a credit transaction:

MerchantID (I didn't see this in the JSON definition for Transaction) TranType TranCode InvoiceNo Accountinfo: (Track2 or AccountNo for keyed) Amount

if no mag (track 2) is available then expiration(ExpDate) is required separately. Expiration is typically in the track2.

With your original JSON request we can change the JSON to if a swipe.

"{\"TransactionId\":\"0\", \"TranType\":\"Credit\", \"TranCode\":\"Sale\", \"InvoiceNo\":\"123\",\"RefNo\":\"0\", \"Account\":\"\",\"Amount\":\"69\"}";

if no swipe then it is a Keyed entry and requires:

"{\"TransactionId\":\"0\", \"TranType\":\"Credit\", \"TranCode\":\"Sale\", \"InvoiceNo\":\"123\",\"RefNo\":\"0\", \"Account\":\"5499****\",\"Amount\":\"69\", \"Exp\":\"MMYY\"}"

These are optional but should be available for Keyed entry for a better credit card rate. += "{\"Address\":\"

\", \"Zip\":\"81301\",\"CVV\":\"123\"

mozvat commented 11 years ago

Comment via Dan Ourada Save information about transaction at MPS so that POS developers do not need to do that work. If there is a value that MPS is returning to a developer that they will never need for any business purpose that’s a good candidate for keeping it on the MPS side and appending it to transactions when necessary. AcqRefData, SeqNo, ProcessData, etc. are all good candidates for this.