Re: Bank transfers -- multi vs single access log-in

[Davi Leal]

Antenore Gatta wrote:
> Nicodemo Alvaro wrote:
> > I don't understand how I will be able to do testing on my own if the
> > project will need a bank account to be managed. Will the bank give us
> > a test account so that we can see how things work?
>
> No, at least not for a small "business" as Gnuherds.

Just noting I think GNU Herds wants to be a "non-profit true-democratic 
association".  Reference:  http://gnuherds.org/   Anyway people could expose 
her own opinion about it.


> We need a so called "business account", where is (not always) possible to
> share 1 bank account with different logins and ACL.
> The banks that provides these kind of multi-access, they sometimes provide
> also API, tools or third party tools for online shopping or onlline
> transactions.
>
> So first of all we need to identify banks that provides these kind of
> services.

As it has been proposed, we should work it out by phases.
I propose begin with two phases:

  1. Finish the current functionality drafted at the below links, without
     adding the bank account support:

       http://gnuherds.org/volunteers
       http://gnuherds.org/pledges
  
  2. Think about how to add bank account support, etc.


> > Would the client or the GNU Herds' servers be doing to the sending
> > actions to the bank's servers?
>
> Will be the GNU Herds server that will send the transaction using the
> provided bank's interface

I am not sure yet. There are security risks.  We can follow analyzing it, 
taking into account it will be worked out at phase 2.


> > I don't quite understand the advantage of ING Direct other than the
> > 3.15% annual yield. I believe for ING Direct to work you need to keep
> > another checking account with another bank.
> >
> > http://business.ingdirect.com/products/ofb_savings.asp?s=OpenAccount
> >
> > I'm agree, as we need in any case a bank account I don't see any
> > advantages
>
> using Ingdirect, they even not provide APIs or tools for online
> transactions. BTW, it could be interesting to have it additionally for the
> 3.15% annual yeld.

Now I think both you, Nicodemo and Antenore, could be right about this 
subject. I was missing a lot of things. I was wrong :)


> So, resuming....
>
> We need to choose a bank that provides API, tools, interfarces and so on,
> plus multi access login.

IMHO, it is not clear yet the webapp will access to a bank account using multi 
access log-in.

Maybe sereval of you could follow analyzing the bank related subjects
(phase 2), while I follow with the (phase 1) tasks. Sorry, I am a bit 
overloaded!

The key question is:
  What bank-related functionality will the webapp offer to their users?


> As they usually provide access only via PIN/TAN systems, we have to choose
> carefully, and to choose carefully who will hold the access keys (RSA keys
> or whatever).
>
> Or we can choose any bank accounts and using a platform like ePay (Visa)
> http://usa.visa.com/merchants/payment_technologies/epay.html?it=c|/merchant
> s/|Visa%20ePay
>
> I know it's kaotic... Well I advice you, if you are still interested to
> start to see, just to have an idea, what your bank offer, and asking to
> them what would be needed if you would like to add online transavction to
> your business, be vague, don't specify which is the business.
>
> I hope that I didn't add more confusion, and as usual I could be wrong.