I have a question regarding the Paypal Java API. I read their documentation and watched some tutorials about their developer tool to integrate Paypal in my app, but I didn't see nothing about letting users pay each other through Paypal.
To be more explicit, for 2 users, user provides a service through the app for user 2 and user 2 now has to pay user 1 through Paypal within the app. Is it possible, and if it is, how ?
From what I read, the only way I can think about doing this, Paypal API can send an invoice to user 2, but from me (from the application as the receiver) and so the money would go to the app account (express account or whatever it was called) and from there I could forward the money to the user 1. This way would be really inefficient and I wonder if I could make the transaction directly: user 1 sends an invoice to user 2 and user 2 pays that invoice directly.
Thank you.
You can use Adaptive payment API to let user 1 pay user 2 directly, the app act as the API caller, please see document here
Related
Hey I want to develop a website which basically allows customers to visit my site and add orders to there cart. On check when user enters payment credentials i basically want to submit a process to alibabas webpage to the direct order linked to on my webpage, and place an order through the site using there shipping/billing and payment info. That way when they complete checkout on my homepage alibab will have sent me an email saying i have order and item for (user inputfields from my webpage from) and all the other info alibaba sends on there checkout. Basically all orders will go through my account, but there will be different shipping and payment methods..
If something like this is possible could someone possible point me in the right direction to creating something like this?
I don't mind creating a java web applet for this e-commerce site.
Integreted inAppPurchase Most of Orders display That Payment Declined
only 1 succesfull purchase out of 7 or more order
most of orders goes Payment declined
seee image atteched hereSee Image
First, this does not belong to stackoverflow because its not a programming question.
To answer your question, not all purchases are successful. The user's payment could be declined for various reasons and you can do nothing about it
I don't clearly understand - how Apple Pay works in case of online checkout via online store.
From my understanding:
Prerequisites:
1) Card which will be used for payment should be added to Passbook.
2) During adding this card to passbook Apple device sends request with PAN to issuer and if verification is passed - format unique token, which is stored in AppleSecurity element.
When customer try to make purchase online via online store: 1) customer should switch the card, which will be used for payment 2) Store formats the request with total amount, shipping address and token, which is stored on Security element 3) Apple device sends request to AppleServer for payment authorization 4) After this store can executes additional logic (whatever)
Feel free to correct me if I'm wrong.
But my question is - if existing system already uses tokenization service, payment gateway and payment processor - how it can be integrated with Apple Pay?
You need to look at the documentation on Apple. Your description of the way apple pay works is correct in the first part, and incorrect in the second part. There's a good tutorial on Apple Pay at Ray Wenderlich.com that shows how to implement it.
Here's a general description:
Within an app, Apple Pay is just a source for payment details. The app is responsible for
creating a payment request (with line items and a total)
triggering the apple pay interface
checking any shipping details
contacting the back end or a service (Stripe, etc) to create a token for the specific purchase
sending the successful purchase token to the app's server to record the purchase
So there are two tokens needed: one for the user's payment details (the card) and a second token for the actual purchase. In loose terms, Apple Pay is responsible for generating the first one, but the app + some service is responsible for generating the second one.
I'm using Facebook Grap API tool
to simulate queries before I run them from my android app.
I want to get the users' likes and interests.
However i think the result doesn't include all the user likes and interests.
what is the default number it returns?
how can i ask for all the items?
I am building a site that sells tickets. I am processing payments through third party payment processors, google checkout. Currently I am limiting purchase time on google checkout to 10 min. If they take longer, the tickets reopen and other users are able to purchase the tickets. The only problem is that Google checkout doesn't know that the timer has expired. The user is able to complete their purchase even though the tickets they are trying to buy have already been bought by someone else. Is there any way to stop google checkout from selling too many tickets? The tickets are GA so if I could limit how many are sold total this would work also. If this is not possible, which seems to be the case, has anyone tackled this problem and found a better solution?
You have several options to deal with inventory issues:
Checkout Store Gadget: offers a simple built-in "inventory update" (using an online spreadsheet). Because Google handles the inventory, an order will not go through if the inventory dropped to zero. Here's the link to the Store Gadget documentation:
http://code.google.com/apis/checkout/developer/Google_Checkout_Store_Gadget_How_To.html
If you don't want to use the Store Gadget, you can use the Checkout Notification and Order Processing APIs and cancel the order if it took to long to complete (i.e. the ticket was sold to someone else). This avoids overselling but will make some customers unhappy.
http://code.google.com/apis/checkout/developer/Google_Checkout_XML_API_Notification_API.html
http://code.google.com/apis/checkout/developer/Google_Checkout_XML_API_Processing.html
Use an inventory buffer to avoid overselling. Keep a few tickets in "reserve" and avoid cancelations and unhappy customers :-)