These are chat archives for CORE-POS/IS4C

23rd
Jun 2016
Finn
@thefinn93
Jun 23 2016 18:45
@gohanman looks like PaycardRequest and PaycardResponse are both for after the card is swiped, just like, tracking the response from the payment processor
right?
cuz with the pax device, it handles all that, i say "Charge them $5" (via an HTTP API call) and it prompts the customer to swipe their card, asks for the PIN if needed, then ships it off to the payment people and then responds to my HTTP request with the result
so PaycardRequest object wouldn't really be needed.... idk
Andy Theuninck
@gohanman
Jun 23 2016 18:49
It's basically write what you're about to send to the database (w/o full card #s, of course), submit request to the process/device/middleware, update database record w/ info about response. It's not strictly necessary in the sense that the transaction will still process, but it's handy to have a record of what happened. You could just use plain old SQL to interact with the translog.PaycardTransactions table instead if that's easier
Finn
@thefinn93
Jun 23 2016 18:50
I guess i was thinking I'd just use the PaycardResponse stuff becuase I don't get it before it goes to the processor/device/middleware
like, the device takes the CC# and sends it where it needs to go, and I never see it
i think i get the last 4 or something
idk
Andy Theuninck
@gohanman
Jun 23 2016 18:55
That's what happens with the Datacap (ActiveX control) transactions, too. Both these classes are just wrappers around that PaycardTransactions table. PaycardRequest creates a record & PaycardResponse updates that record. It doesn't make much sense to use one w/o the other. There's nothing HTTPS oriented in them
Finn
@thefinn93
Jun 23 2016 20:06
oh okay
sounds good