I'm having a data issue I'm not sure how to handle.
Scenario: A company has a shared credit card. Which means, it is one account, but two people have access to the account, each person with his own credit card with his name on it. Let's call these people Charles and David, and assume they have a Chase account.
When I add this Chase login to Yodlee, it pulls the account THREE times, as:
"Chase - Credit Card - CREDIT CARD"
"Chase - Credit Card - DAVID"
"Chase - Credit Card - CHARLES"
It does this even though they are the same account. (I guess when you login to Chase it shows up multiple times).
All three are coming in with different ID numbers. So there is no way for me to know they are all the same account. My code thinks they are three different accounts, because they have different names and ID numbers.
As a result the account gets stored in my app three times, and the transactions three times.
What do you recommend?
Here are some suggestions:
First thing is to look for a particular site i.e., if Yodlee supports the Business Card site for that particular institution or not. As sometimes some of these Bank websites have a different login URL which can be either accessed by a different credentials or might be by the same and that will show you only 1 actual credit card account instead of 3.
In case the Business site is either not available or not supported by Yodlee(though you can request Yodlee to support the site and it could be prioritized based on the business use case), else you could call deactivateItemAccount API. This will deactivate a particular itemAccount and you can call this for those duplicate accounts.
Related
So I am building an app with react-native (expo) where a user fixes appointment with some other person and to do so, he has pay the other person.
Now how can I handle payments here. What i want is the user makes the payment and the receiver should be the other person but how much i understood the payment gateways, the payment is received by the app owner or in simple words, receiver is a single person.
I also tried deep linking to directly take the user to some UPI app like google pay or paytm but it seems that those apps require some special type of account (merchant account) to make the transaction if we access them using deep links (which is a problem as it is not necessary that every user will have a merchant account).
As I said, it is always better that you have your own payment gateway account, and all the transaction goes through your gateway, meaning you get the money and you build a system which will forward the payment to the receiver. I have worked on 2 such apps:
1: Where we have our own razorpay account, and we get the payment first, and then we forward it.
2: Where in we were directly having transaction between 2 users, but not through app, instead we display them the account details of the receiver and give them 48hrs time to pay that account. But we had to manually handle this scenario since one cannot know if the user has paid to the said account, since it's not your account.
3: There is one more method where in payment gateway has a webhook which consists of a virtual account number, and every user that lands on your app, you can create a virtual account number for him/her and store the user-virtual account number relationship in your db, whenever there is a payment, you can find out about the user through this virtual account number. Read about this.
The deep link is a good idea, but again, as you mentioned, it will require the end user to be a merchant user(have a merchant account), you can find more details here
Maybe you can ask your users to create a merchant account, which again I am not sure if it's possible, and if it's possible, if it's feasible?
The best way according to me is, you handle this through your payment gateway, and instantly forward it to the user who should have received it. Again there are some rules and clause to it(some commission is taken by those payment gateway,etc), check those things out.
I think the most close answer to my question is to use razorpay routes where we can link multiple accounts with our account and transfer money accordingly.
More details here
We are building an iOS app that uses Yodlee API's to retrieve credit card transactions for our users.
Right now, we are using FastLink API to connect.
Once accounts are added to a users profile, is there a way to filter the transactions for a specific account by credit card? (For credit card accounts that have multiple cards associated with them)
For example: I have one credit card account with 4 cards associated with it. I am trying to retrieve only the information for a single card. Can this be done?
Yes, you can get a particular credit card account by calling Get Account Details API-https://developer.yodlee.com/apidocs/index.php#!/accounts/getAccountDetails
by passing the accountId and container as creditCard.
Hope this helps.
I would like to access the list of PayPal Giving Fund charities so that a user of my site/app could eventually donate via credit card or PayPal.
I have looked into other APIs, like Just Giving, Orghunter, Charity Navigator, all in which don't have a large variety of charities.
If you've ever visited the site https://www.humblebundle.com the idea is very similar to this. To give you an idea, it'd go something like this:
I select charities for the user to donate to for a certain category (environment, animals, etc), save to db to retrieve specific charities later
User sees charities to divide their donation using sliders. They have the possibility to swap out charities if don't like selection
User enters amount and enters their credit card or paypal account
I make the connection to PayPal API to make donation
User then gets a receipt or something like a tax receipt
I guess the questions I'm asking are:
Is there access to a list of Giving Fund charities via an API
Is it possible to donate to charities from the Giving Fund list via the API
Would this API be available to an Australian PayPal account
If there is no API for Giving Fund, is it possible to retrieve a list of charities to do this via another route in PayPal
Will there be any restrictions on the Apple and Android stores if this was an app
Thank you so much for your time!
Have you checked out www.pandapay.io ?
To answer your questions:
Is there access to a list of Giving Fund charities via an API
PandaPay has a database of every 501c3 in America, check out Pandasearch: panda-search.s3-website-us-east-1.amazonaws.com
Is it possible to donate to charities from the Giving Fund list via the API
Yes, check out www.pandapay.io/docs
Would this API be available to an Australian PayPal account
PandaPay currently only works for USD, and payments to US-based charities. That being said, most international charities have a US branch to access the American charity market (largest in the world, by far)
If there is no API for Giving Fund, is it possible to retrieve a list of charities to do this via another route in PayPal
Is PayPal really a necessary factor for your use case?
Will there be any restrictions on the Apple and Android stores if this was an app
PandaPay is closely modeled on Stripe's API, and thus iOS and Android SDKs can easily be written for easy usage in mobile applications.
PandaPay API: https://www.pandapay.io/api-reference
Stripe Example: https://stripe.github.io/stripe-ios/docs/index.html
OrgHunter can authenticate more 501(c)(3)s (affirmative or revoked) including a large number of those with affirmative determination by virtue of the fact that they are subordinates of "Group Exemptions".
In addition, the OrgHunter database includes the most robust set of charity data attributes.
Access to the dataset/platform is by API or WordPrss, Drupal, Concrete 5 plug-ins. In addition, there are .NET and standard PHP implementations.
Comparing Just Giving, Orghunter, Charity Navigator, and PayPal Giving Fund is like comparing apples to oranges to bananas to kiwis.
Just Giving focuses on tools and systems for charities, corporate programs, and campaigns on an international basis, although they did just "acquire" the assets of "JustGiving.org" as a way to expand their footprint in the United States. OrgHunter is a platform supplier inclusive of data, donation processing and compliance, upon which tech philanthropists build software and web apps connecting and routing diversity of donors to diversity of charities. Charity Navigator focuses on ratings. And finally, the PayPal Giving Fund serves PayPal customers by enabling them to make donations to a charity of choice with the following two requirements/caveats. 1. A charity MUST ENROLL in the PPGG to receive donations from the PPGF, AND 2. to receive grants, the charity MUST ALSO create a PAYPAL ACCOUNT into which the PPGF will deposit donations. Unless the policy has changed within the last two months, the PPGF will ONLY deposit grants into a PAYPAL account, otherwise the donated funds are distributed elsewhere. This is in part why the PPGF is now dealing with a class action lawsuit that asserts that PPGF was engaging in deceptive practices.
A couple of comments about your idea, particularly as it is reflected on https://www.humblebundle.com.
In all circumstances, the moment someone starts doing any sort of fundraising online, they are subject to the various fundraising and solicitation regulations of the 50 states, because "online" by definition crosses state and international borders. The IRS may determine if a charity is a legit charity, but the states govern and regulate the conduct of fundraising and solicitation.
People cannot solicit for a charity or use charity brands or trademarks without explicit permission. That means that if you want to feature, promote and fundraise for a particular subset of charities, you will need to get the charities to opt-in or buy-in to your process or program. There are companies that do this, however it is a daunting, full time job.
An alternative to enrolling and managing charities is to give users/customers the opportunity to designate a charity of choice, and thereafter "route" their contribution through a 501(c)(3) "Donor Advised Fund" to the destination charity. That is what the alliance of OrgHunter and Make My Donation do. They integrate the most dependable charity database with donation processing and regulatory compliance into a cohesive platform that is easy for software and web app developers to build into their applications that are used to support all sorts of good causes.
Evening
I have a client who is asking to build an eCommerce tool in which multiple stores are able to create accounts and their products in order to sell them via a web app.
This is not like any regular eCommerce sites since we are working with multiple stores each one of them with an unique bank account.
The quick solution is to ask the stores users to give me the bank account and all extra sensitive information and do the transaction via coding my self... but i don't want to mess with such delicate data that is why im looking for some service that helps me do that.
I know that i can use auth net to build something like that but my main client will have to pay for each of those merchant accounts, which is not a very good option.
Any of you had the chance to work in something like this before? Can you tell me which services you used? Would be extraordinary to use the same payment gateway to do everything but i am probably asking for too much...
Waiting for answers, thanks in advance
You definitely don't want to be storing bank information and card data if you are not Level 1 PCI compliant. There is a lot of financial liability if you do so.
There is a company called Base Commerce (www.basecommerce.com) which allows developers such as yourself to create a 'partner' account and associate multiple merchant accounts under it. You can spin up or down as many accounts as you want, all programatically, at no cost (except for the small % transaction fees that are normal in payment processing). You will also get commissions on the transactions your merchants process.
I am so confused about the services and over here the paypal website also seems to be serving up 400's and 404s.
This is how the webpage looks for customers on my site when they are ready to pay:
As far as I know, I don't have Express Checkout, but I'm not sure if I have Website Payments Pro (my company created this account).
Now I have two questions:
1- This is just the sandbox. But on the real site, does this solution that give users the opportunity to pay by credit card? I've actually successfully done a credit card transaction in the sandbox, I'm just worried because I've heard that customers can only do direct credit card transactions in PayPal Website Payments Pro. The PayPal website is overloaded with information and I can't find my way around it to answer simple questions like this.
2- Is it possible to do negative testing for transactions on this page? Such as simulating the events that the user's credit card or Paypal account doesn't have enough balance? If it is possible, and I am using the ButtonManagerAPI, then is the technique below the correct way to go about it?
I put an error code in the amount variable that is passed on to IPN via via an NVP api call, like this (lots of value pairs in the middle excluded as irrelevant):
$nvpReq = "BUTTONCODE=HOSTED&..............&L_BUTTONVAR1=amount=".$err_code
EDIT
So it appears I have PayPal Website Payments Standard, which means I cannot incorporate cannot have credit card payment forms directly on my website, but customers have to be directed to PayPal. I'm fine with that, as long as customers have the option to pay with credit cards.
The screenshot looks like PayPal Standard, which is an HTML-only (non-API) integration.
Any regular business account that can receive money can make use of the Express Checkout API.. typically by authenticating with an API USER/PWD/SIGNATURE. For businesses with programming/development resources, EC is by far the recommended way to accept PayPal payments.
If you pass SOLUTIONTYPE=Sole in the initial SetExpressCheckout call, it will accept credit cards from "guest" customers who don't have a PayPal account, similar to the Standard screenshot you're displaying above.
The main reason to choose EC over Standard is that it's a much tighter handshake between your checkout software and PayPal's servers. With Standard's HTML-only, the customer is redirected away from your site and might not return to your site after a successful transaction is committed (they may stay on paypal.com and not click to return or their browser might crash before return --- whereas with EC the return to your site is built-in before anything touches the financial system)
With the recent beta of developer.paypal.com, all new sandbox Business accounts are full Pro accounts by default. Signing up for a live Pro account would be useful if, in addition to accepting PayPal payments, you wished to create a credit card entry form directly on your own site.
Here are some EC links for programmers:
https://tryit.paypal.com/guide/ec
https://paypal-labs.com/integrationwizard/ecpaypal/main.php
The button manager API is unlikely to be useful to you. And there are ways to do negative testing with the sandbox, but it's really not an important concern when you're still deciding on a product/API.