What precautions should you take when building your first billing and payment system?
Payments
Asked by Question Bot01/Oct/20131 answer
1 Answer
F
Faisal Khan
Answered 01/Oct/2013
Your framework / process-flow needs to be really well though out. One of the biggest delays on a payment software development project we were working out on was that even though we thought we had documented it throughly, it wasn't enough.
Once you start coding, additions will come your way, that you cannot afford to ignore. Check for fraud or balance or authentication, etc. will prop up mid development and you need to be able to take care of these things.
Our way forward was to stop mid way redo the entire process flow in excruciating detail. Once this was done, we had very little interruptions during the coding process.
Bugs will always be part and parcel of your development. Your use cases will bring them out. Do not worry too much about them. The important thing is to get the skeleton code out and working.
However, this does not mean that your coding is extra-ordinarily sloppy. You need to be able to code properly, just don't be overtly concerned about each and every portion to be bug/error-less.
Once you start coding, additions will come your way, that you cannot afford to ignore. Check for fraud or balance or authentication, etc. will prop up mid development and you need to be able to take care of these things.
Our way forward was to stop mid way redo the entire process flow in excruciating detail. Once this was done, we had very little interruptions during the coding process.
Bugs will always be part and parcel of your development. Your use cases will bring them out. Do not worry too much about them. The important thing is to get the skeleton code out and working.
However, this does not mean that your coding is extra-ordinarily sloppy. You need to be able to code properly, just don't be overtly concerned about each and every portion to be bug/error-less.