I need to learn this subject.
Question 1: Is there someone who can point me to suitable info or a Debian package that does the job?

I assume this still needs human intervention to authorise the transaction and I need to avoid this. For example I have a list of filenames, each of those files must be provided by someone whose bank details we have and I need the payment to be authorised automatically after the software has checked the file received is of an expected length.

Question 2:Would the answer be part of the info mentioned above or is someone aware of how to resolve this particular problem or can suggest how to do it.

Thank you for your help.

Google got me this, which should at least be a good place to start:

How can I write software that does bank account transfers?

My first impulse when I read your question, btw, was to say "ask the bank."

1 members found this post helpful.

Not if it is pre-authorised by the payer. This is usually for specific recipients and is used for systematic investment in funds, loan repayments etc. Technically, your programme will work even if not pre-authorised

Since you are mentioning files with data, I assume it is for periodic bulk payments. Bulk payment / receipt gateways exist in almost every banking system. Most have a predefined format in which you have to submit data. In India for instance, the most well known is the "Electronic Clearance System" managed by the reserve bank of india (like rba in australia). It is ideal for bulk transfers and has a standard text only format that can be encrypted at source. Similar facilities exist in all banking systems. As dugan said, "ask the bank".

I googled "bulk payment processing systems in australia" and got many links like:
http://www.sydneyecommerce.com.au/?g...O-IaArV_8P8HAQ
http://www.paymenthub.com.au/directd...SuQaApWD8P8HAQ

The programming approach would be to confirm the formats from the banks and develop routines for validating data, sending data and receiving confirmation, error lists (no cash, recipient account closed etc) and so on. These routines should be developed such that they can be plugged into other client software.

OK

2 members found this post helpful.

You also need to ask the bank for their test interface to make sure that you completely validate your code. Simple mistakes could get very expensive.

1 members found this post helpful.

Thank you for your answers.

AnanthaP, is there anything else you could add to your answer when I clarify my explanation a bit?

It is not for bulk payments, the files I refer to could be send by anybody who accepts to work for us, from anywhere in the world and the payment needs to be made to a bank nominated by that person, also anywhere in the world.

As an example such a person accepts to translate the content of a file in another language, that person, whose details (less bank details) are in our databases, informs us of the fact and let us know their bank account details so we can pay when we receive the translated file. If we receive the translated file within the allocated period of time, we want the payment to be done automatically (we found it a lot more convenient for many reasons to take the risk of making a payment for junk rather than verifying that every file sent to us meet our requirements before making a payment). Needless to say our software also needs to check our bank account has the money before paying.

i didnt find this response useful but i found it very informative:
http://www.linuxquestions.org/questi...8/#post4336852

its about paypal but it mite illuminate to you the general process (especially since i dont think this is cookie-cutter. every bank/site mite have different methods).


good luck,

1 members found this post helpful.

It might help to think of it this way: this is how most businesses pay their employees (direct deposit), and it's generally handled by payroll software.

1 members found this post helpful.

Ohh. I thought that the files were payment data files. I get it now. They are the product for which you intend to pay the persons. Payments "anywhere in the world" are tricky. You get regulatory issues (in both Australia and other receiving countries) and also exchange rate volatility. Better check it with your law and accounts persons.

dugan is correct. Ask your bank and get the details of formats, controls, test interfaces etc. Then you should be able to plug it into your application.

Additionally, if a payroll system is not acceptable for some reason, a finance system that treats the payees as sub contractors will have the desired functionality and also be able to check your bank balance.

OK

1 members found this post helpful.