[Openid-specs-fapi] How do I find AccountID to use in transfer?

[Saxena, Anoop]

Hello Nat,

Transfer API is for transfer between user owned / or have permission (such as Joint/ custodian) accounts within a bank.

This is not for making a transfer between two accounts owned by two different customer with no relation within a bank.
This also not for making a transfer between two account from different bank.

DDA did not go that far to solve for these use cases

Thanks,

Anoop

From: Nat Sakimura via Openid-specs-fapi <openid-specs-fapi at lists.openid.net<mailto:openid-specs-fapi at lists.openid.net>>
Reply-To: Nat Sakimura <nat at sakimura.org<mailto:nat at sakimura.org>>
Date: Tuesday, August 2, 2016 at 1:14 PM
To: Openid-specs Fapi <openid-specs-fapi at lists.openid.net<mailto:openid-specs-fapi at lists.openid.net>>
Subject: [Openid-specs-fapi] How do I find AccountID to use in transfer?


Hi Anoop,

Reading DDA, I was wondering about this.

When I want to transfer money from one account to another, I seem to need FromAccountID and ToAccountID. How can I find the AccountID? Is it the Access Token or Refresh Token?

Do I need a permission of the Account Owner to send money to his account?
How do I get the AccountID that represents the other person's account?

In Japan, typically, a sender needs to specify:

* BankID
* BranchID
* AccountType
* AccountNumber
* AccountName in Katakana

(These probably varies depending on countries.)

Then, the sending bank makes a request to receiving bank to verify that these details matches and creates a transfer object with the amount entered by the user and the user's withdrawal account details. The user must specify from which account the money should be withdrawn.

This transfer object is then shown to the user, and the user commits to it.

>From an API point of view, there would be an accountInfo object such as

accountInfo
    BankID
    BranchID
    AccountType
    AccountNumber
    AccountNameKana

as JSON which is sent to accountID endpoint of the BankID that returns accountID, perhaps unique to the transaction. This endpoint would be a protected resource, and would probably requires the access token issued to the originating bank or the payment initiating service.

Then, it does the same for the account that the money is withdrawn.

Then,  the resulting transfer object would become:

{
TransferId:
FromAccountId:
ToAccountId:
Amount:
Memo:
PaymentDetails {
    PrincipalAmount:
   FeesAmount:
   }
}

Another question about the AccountID is that it may not be globally unique unless there is an issuer component to it. How is it being managed?

Also, for the transfer object, it feels much better to explicitly stating the FromAccount currency. (I read that "Amount" is expressed in FromAccountID currency. )

Best,

Nat Sakimura




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-fapi/attachments/20160808/074043ae/attachment.html>