Can balanced accept bank account from other countries apart from US?
If yes how the routing numbers and account number format should be?
Also
When am creating a test bank account using balanced.js, the account type is set to 'checking' even though i sent type as 'savings'. Is the test bank account always has type 'checking'?
No.
https://support.balancedpayments.com/hc/en-us/articles/200135940-Is-Balanced-available-internationally-
https://support.balancedpayments.com/hc/en-us/articles/201886494-International-ACH-Transfers-IATs-Not-currently-available-
As for the account type issue make sure you pass "account_type" instead of "type" for balanced.js v1.1.
Related
If I check that the institution supports auth as a product, would account number and routing number be guaranteed to be there in the numbers field in the auth response?
Sort of.
If the account is from a US bank account, AND if the call doesn't result in an error, you're guaranteed to get account number and routing number. However, that doesn't mean that all Auth calls will return account + routing number.
For example, Auth if you call Auth on an Item that just has a credit card account, you'll get an error response back [this prevents you from getting billed for calls that don't return anything useful]. Or, if you call Auth on a bank account that is from outside the US, you'll get the numbers associated with the transfer system used by that bank (account number + routing number is a US-only system).
I am working on a sample banking code in solidity. I wanted to use a so called "TakeAllTheMoney" and run function (just to give you an idea about the role of the function).
This function should only be executable by the deployer of the contract and should give him the possibility to take all the money on the bank and transfer it to his account.
Problem: How can I empty also the account of the other user of the bank? Meaning that when a different user - not the deployer of the contract and of the function - uses the contract after the "TakeAllTheMoney" function is employed, he also sees 0 on his account.
Many thanks in advance
function TakeTheMoneyAndRun() public{
require (msg.sender==Owner);
balance[msg.sender] -= balance[msg.sender];
(msg.sender).transfer( address(this).balance );
Expected results after employing this function:
Balance Bank = 0
Balance person that employed contract and function = 0 (since it went on his metamask account or similar)
Balance of every other user = 0
Again, thanks!
You are mixing two things. User's amount in metamask and user sent amount to Bank in your case is Smart Contract and stored in some variable. So the amount you see in the metamask is the amount User own and has no link with the Smart Contract until and unless you send the money to the Smart Contract.
The Smart Contract in your case "Bank" the money sent by the user is store in the Smart Contract and the tracking of money recieve is stored in the array. Smart Contract itself does not holds the record of the previous transaction. So if you want to delete the Smart contract balance tracks of the User you have to empty that particular array. Although it sounds fishy if you want to implement it and wants to make the user accounts to zero in the Smart Contract.
As per the api description the call : getItemSummaryForItem1 should be used to fetch the itemAccountIds for a site account. The response of this call has only last four digits of the account number. I need to identify which item summary corresponds to which account in the list of bank accounts under this site account. Is comparing the last 4 digits alone is sufficient?
Thanks.
You need not call getItemSummaryForItem1 to get itemAccountIds for a site account as Yodlee has enhanced the response of getItemSummariesForSite which now returns both itemID and itemAccountId hence you need not worry about any mapping.
Just to answer the last part - Yes the last 4 digits of the account number is enough.
Is there an Api that will give me access to a consumers full account numbers (non-masked)
Using: getItemSummariesForSite will bring back a list off accounts, however the accountNumber is masked.
Thanks
It depends upon the site, if FI provides the non-masked Account number then you can get it. But you need to connect with the Sales Representative for the same. By default you'll get the masked account number.
How do the rest of you handle complex names when submitting a transaction to Authorize.net using AIM?
Nearly every ecommerce application on the planet asks the user to fill in the "Name as it appears on your credit card". For some odd reason, Authorize.net wants you to submit x_First_Name and x_Last_Name however.
This is fine when you're dealing with Mary Jones or Jack Smith. It becomes a real hassle when you've got Margret A. Jones-Robinson and H. William Robert Van Horn, Sr. though.
Is there a best practice here?
First & Middle names in the x_First_Name field?
Last Name, Hyphenated Name and/or Suffix in the x_Last_Name field?
Has anyone developed a routine to parse names accordingly?
Thanks!
Have two fields on your payment form. One for their first name and one for their last name. However the customer chooses to complete the form is how you should submit it (and save it in your database if you choose to do so). FYI, the name on the credit card is not used in the processing of the credit card so you do not have to transmit it to Authorize.Net to process the transaction. You should do it anyway as it helps to keep your records accurate and complete which is handy when doing audits of your transaction history.
You should generally try to avoid using one field for names as it opens up the possibility for people to enter bad information like, "The Smith Family" or "Barabara and Steve". By having two clearly delimited fields you greatly reduce the occurrence of this.
You should use 2 fields on your payment section. First name and last name.
The name on the credit card is actually used by certain cards for some services, so if you signed up for AVS and fraud detection they will use that name and provide feedback as to if its a match or not.
Alternatively, and what we have done in the past is ask the customer for:
-prefix
-first name
-middle initial
-last name
-suffix
This allows the customer to feel in control and you avoid them filling garbage in the 2 main fields (first name, last name). Authorize.net and other merchant service providers dont care for then other fields and you may choose not to either, it is just a way to keep the data "cleaner".