I have integrated Paypal-SDK with my Android Application This is
working fine when i am using PayPal, but when i am using direct
payment with credit card it crass.... how can make direct payment
using PayPal sdk.
Even the application i have created is showing like that.see the line features that are not - available for live transaction
Now more thing how can i get test credit card details including
cvv so that i can request test transactions in sandbox mode.
In my case, Its giving this Disclaimer:
"Unfortunately, due to recent product changes in the region, we are no longer able to allow Live DCC processing via RESTful APIs to Canada. We are continually looking for ways to expand our services, so please stay tuned. We apologize for any inconvenience this may cause"
This mean that, paypal does not provide Live DCC processing to some areas in "Live api" (you can test it in test Api), you should check if it is the case with you. Either show your log cat.
While Using Test Api, two accounts are generated, one business account, another personal account. You can test it by transferring some amount (not actually transferred) by personal account in your app and check it in your sandbox business account.
It may help you.
Related
I'm using Google Pay with Stripe on Android.
I'm part of the testing Google group, so I have the list of Google Pay test cards that I can test with, but they all succeed. I've been unable to add Stripe's cards that give specific failures to Google Pay.
I'd like to be able to test failing for insufficient funds for example, where the card is valid, it just fails to actually charge.
I've been able to reproduce some of the errors in production, for example by using a card with a $0 balance, but I have to do this on a release build and don't have access to the debugger, which makes tracking down issues a lot harder.
What's the best approach for testing all the various failure cases with Google Pay?
EDIT: I'm able to mock responses and do testing that way, but the errors in production don't seem to act the way the documentation would lead me to believe, so I'm having trouble mocking in a way that actually matches production behavior. Would be nice to be able to end-to-end test with Stripe's test cards in Google pay for example.
Google Pay won't typically return information related to things like insufficient funds. The reason is Google Pay will perform some authorization checks when the card is added to Google Pay, but not when the user selects a payment method.
When a user selects a payment method with Google Pay, it returns a payment token that you would then pass onto your PSP (Stripe) and Stripe would respond with insufficient funds (and other scenarios). Therefore, it comes down to how your Stripe integration responds with the payment data specified. My suggestion is to stub/mock the request to Stripe and return your desired response instead. The response from Stripe would typically need to be handled in your back-end code and sent to your Android app with details of the failure (e.g. insufficient funds).
I'm currently developing a mobile application which will list businesses in a marketplace type format i.e. individual business listings, allowing users to purchase smalls items through our application.
Ideally each individual end user will be able to select their desired payment method such as PayPal, Mastercard or visa during sign up; however, we would also like to provide the option to change their desired payment option at a later stage.
The payment details saved by the end user will be stored and then delegated to the businesses at the end of the month etc.
Payment to the businesses will be made at end of month less our fees/subscription.
We conducted research and decided PayPal Adaptive payments to be the ideal option for chained payments to each business; based on the review of Braintree, Stripe and PayPal. Braintree was our next option however they don't offer their marketplace solution to customers outside of the US.
We have attempted to contact PayPal Developer support on numerous occasions, though have not had much luck in confirming what is required for a complete end to end solution based on our needs.
Our questions for the community are, will PayPal adaptive payments allow for the following:
Provide our end users (purchasing user) the option to choose between PayPal and other credit card options such as Mastercard, Visa, ApplePay
Store user payment details and allow for future updating of payment option
Allow Scan card API so a user scans their credit card using native IOS or Android camera?
Allow for top up type functionality so a user can add funds and top up when funds are low?
Our developer has not worked with the PayPal Adaptive solution, however, believe we cannot implement the above requirements with the Adaptive payment option.
The community we need your HELP as we are currently at a roadblock in the development of the payment solution therefore if anyone has implemented a similar mobile solution your advice or suggestions would be greatly appreciated.
I hope my questions are clear, though please feel free to request additional information.
Regards,
Wayne
PayPal Adaptive Payments is in a limited release. See this Developer Doc on the PayPal Developer website. Although they will continue to support Adaptive Payments for existing users, they will not likely accept new applications unless there is a special circumstance.
May I suggest looking into the PayPal owned company Braintree Marketplace?
I am working on an app that would require an activation code in order to be used after being downloaded (user will get the code by postal mail). I understand that Apple will be rejecting the App, but can someone confirm if that functionality (activation code for an app) would be valid for Android? And that it could be used.
Before building up a prototype I would need to confirm this fact.
Anyhow, I will limit the audience of my App to Android users as I see that I have no options with MAC.
You should read the Google Play Developer Policies as your starting point (in particular the section "Paid and Free Apps").
If you are using activation codes to bypass app payments or in-app payments, you will be in violation of Google's policies. If the activation code is an integral part of your app's functionality (for example you are sending it by post to verify a user's address) then you should generally be okay.
Disclaimer: I am not a lawyer.
I was using an app once that was later pulled from the Play store because you could purchase some premium features over PayPal (without Google Play). If you intend on charging for this code it might and probably will be an issue, however, if you will distribute the code free of charge to select customers it might work.
But, a better way of doing it would be with a Google Play group. You'd mark your app as beta and make a test group, that would only include the people you want.
But if you want to limit your audience there is really no reason to put your app on Google Play, just distribute your .apk file through your website, and have a serial code as a backup.
My startup is developing a real-time marketplace platform for taxi companies somewhat similar to Hailo, Get taxi, Uber and Lyft (more or less), etc.
We are shopping around for a mobile payment solution and so far, we looked at the products offered by PayPal, Intuit, Braintree, and Stripe.
We are having a hard time with finding the mobile payment solution that fits our requirements.
Requirements:
1) (Must have) Passenger should be able to pay within the app by using previously added payment methods such as Credit Cards (CCs), Paypal (optional). Passenger is asked to enter the CC information only once when they sign up (or add a new card), so the CC info needs to be stored somewhere and retrieved when needed seamlessly. However, we would really prefer not to apply for PCI compliance.
Q.1) Let’s say I use PayPal Mobile SDK 2.* for payment system in our app. In the above scenario (1), is the passenger required to have a PayPal account (even for just using CCs for payment) and link it to our app?
Note: I have spent a lot of time digging into PayPal Mobile SDK 2.0 documentation (also called their support). I was told by the support person that merchants cannot store credit card info with PayPal for mobile payments (which I thought was the whole point of SDK 2.0).
2) (Optional) Passenger should be able to pay with a physical credit card by swiping it in the reader plugged into the driver’s smartphone. However, we need to integrate this process into our app (which is not currently supported by PayPal Here and Square). So, basically we need an API provider that allows creating custom POS integrated with our app.
Q. 2) Am I right when saying that scenario (2) cannot be accomplished with PayPal, Braintree, Intuit, or Stripe?
Q.3) Do you have any suggestions regarding the payment system that would allow us to implement scenarios (1) and (2)? just scenario (1)?
Please help if you have dealt with similar problems or know more about the subject. Thank you
Q3. You can also check out LevelUp. Facilitates in-app payments similar to PayPal and Stripe.
Similar to PayPal, it will allow you to store an access token after the user links their account. You will not be able to charge the card directly, as this would subject you to PCI compliance. LevelUp does not support the ability to swipe a physical credit card.
A. to Q. 1) Yes, the passenger is required to have a PayPal account if you want to enable future payments. PayPal stores and charges the credit card, without the merchant having access to it. This is pretty much the core of the Digital Wallet industry. You might have thought that you could process the credit card yourself, after retrieving it from PayPal. This is not supported, and would subject you to PCI compliance-ness.
A. to Q. 2) PayPal Here does not have a publicly available SDK yet.
A. to Q. 3) Just scenario 1 can easily be accomplished by integrating the 2.0 PayPal SDK.
I am creating an Android application that will offer users a subscription option if the user has his credit card information stored in their device. If he does not, I am thinking about offering different methods for the user to use the application.
Does anyone know if there is a way to check if a user has his credit card information stored in their device?
To clarify what I am looking for:
Android devices allow users to store credit card information so they don't have to re-enter the information for every purchase. I'm talking about identifying that the user has that data stored. I am not talking about storing that information myself for the user or trying to get it. All I need is a boolean method that will tell me if the user has the data stored or something similar.
Credit Card information isn't really stored "on the device." In the case of devices that are connected to the Play Store, Google account credentials are stored and payments are made through Google Wallet. I don't have a lot of experience with other types of devices, but I imagine they all work in a similar fashion, for example a Kindle Fire will keep Amazon account credentials, etc.
If you're looking to create an application that provides in-app purchases and will be available on the Play Store, you can click here to read about Google's In-App Billing API that allows your users to use their Google Wallet to make payments. For Kindle Devices, Amazon has a similar API.
It would be a pretty major security concern if arbitrary apps had access to the device owner's credit card information. If you're writing an app that you intend to distribute outside of a reputable app store and therefore without a built-in in-app purchase api, you're going to have to use your own payment mechanism. If this is the case, I wouldn't recommend creating your own. I believe PayPal has an Android API, and a quick Google search came up with a few other less notable brands that offer this service, though if you do intend to use the Play Store or Amazon's app store, using a 3rd party payment API usually goes against their terms of service.
Edit: The AccountManager class allows you to view info about accounts on the device, however, I don't believe that you can use it to discover if the user has a payment method set up through Google Wallet. I found this SO question that goes into detail about what the AccountManager can be used for. If this is a Play Store app, I'd look into the Google In-App Billing API, it's probably the best option for what you're trying to do.