Timeline for Integrating with a payment provider; Proper and robust OOP approach
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2017 at 12:40 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Sep 17, 2012 at 14:45 | comment | added | ExternalUse | Hi nerdklers, thanks for that - you get a +1 for "log, log and log some more"! I was now considering this approach on "submit": Lock user session. Insert a payment into the DB as pending. Send the request with no "autosettle" (delayed transaction). Update payment record as "transmitted" if successful. Send "settle" command to PSP. Update payment record as "completed", and unlock user session. (Locking means writing a flag to the user's record; should he login whilst transactions are pending he would get a "please call" page.). I'm running out of chars, so I'll put that as answer for comments. | |
| Sep 17, 2012 at 14:42 | comment | added | maple_shaft♦ | +1 I forgot about mentioning how important distributed transactions are. Having to maintain a legacy system that integrates with a PP and doesn't utilize transactions showed me the nightmare scenario firsthand. | |
| Sep 17, 2012 at 14:05 | review | First posts | |||
| Sep 29, 2012 at 16:00 | |||||
| Sep 17, 2012 at 14:01 | history | answered | Niklas Modess | CC BY-SA 3.0 |