I am working on a Rails Application where Users can buy Items other Users shared previously.The payments should be flexible to allow the User who shared an Item to get the money a buyer pais.
1) Is it possible to create Flexible Paypal Payments (Different Seller, different Price for each Item)?
2) Can you use the PayPal IPN with Donations to check whether a buyer paid or not?
3) If not, what is the most efficient way to achive that goal?
Thanks in advance for each answer! Please tell me if you need additional information.
Here's the way I'd approach this:
Is it possible to create Flexible Paypal Payments?
Different sellers: Do you want them to be able to receive the payment directly in their Paypal? If that's the case, you'd need to provide them the details to create a Paypal merchant account and securely store those details, but I don't think that's the approach you want to take;
Most payment solutions provider gives a way to send payment to multiple vendors/merchants, which you may instead want to set up or even in your application, you can set up a kind of payment stuff to ensure that integrates with Paypal's API to pay your vendor soon as you receive payments for items.
So, yes it's possible, the different sellers could be tricky, but all other things are possible!
Can you use the PayPal IPN with Donations to check whether a buyer paid or not?
Absolutely, that's one of the biggest benefit of the IPN is that your application gets to know on time if someone has made a payment. You only have to validate this record with Paypal and, not like it's often necessary compare the payment amount
Related
One of my client Ruby on Rails project have a functionality of get payment from customer in his stripe account.
Now, He needs to pay that payment to the item owner after deducted commission. So, how we can pay from stripe account to particular customer account using API in Rails?
I have checked many API's but not clear which exactly use for it.
Any one have a idea or experience in it?
Thanks
See the Stripe guide on Using Checkout with Rails.
I am not positive if a customer token can be used to send funds to, but if so or not, the following still applies.
If the customer has a connected account (or customer token), you can then use "transfer" to transfer the funds to them.
I am new to the payment area in app. Say in an App like Ritual or Open Table, I want the end user to be able to pay to multiple payees (just like the two apps I mentioned that you can pay to any listed restaurants), how can I achieve that?
From what I understand, each payee could have an merchant ID. If I want to make payment to multiple payees, do I have to obtain all their merchant ID? Or do I collect payment and then transfer to each payees?
Or, is it as app developers, we pick a payment solution (like Stripe or Braintree), and ask the participating restaurant to provide their bank info for receiving payment, and when the end users are paying, they pay directly to the restaurant's bank account through the payment solution.
Thanks.
Not sure if I understand this, why do you need multiple payee? Isn't the customer would just pay he merchant? As long as you can get the merchant ID and their account number, there should not be any issue. No?
Never mind the question, it's basically what I described in the last paragraph of my question
Blockquote
As app developers, we pick a payment solution (like Stripe or Braintree), and ask the participating restaurant to provide their bank info for receiving payment, and when the end users are paying, they pay directly to the restaurant's bank account through the payment solution.
Hello I am integrating braintree in my rails app. I have two roles and one of them pays the amount with a sale transaction to the merchant account. But my scenario is like that I have to then give some of the share to another user for which of course I need to transfer funds to that user account.
Can anyone tell me how am I suppose to do that?
There is a product called the Braintree Marketplace that might solve your problem. The only issue here is that your other user would need to be signed up as a sub-merchant.
I am building an MVC 5 site.
There are multiple vendors with their own product pages
The purchaser is your average consumer. (They may need to setup a PayPal account)
I need to accept payments using PayPal, Visa, etc...
I need to send funds to the respected vendor once their product has been purchased.
Question: What is the best SDK to start with?
There are several different options and I was hoping not to have to go down a road that wasn't necessary
thank you
I need to integrate a subscription solution to my rails application. Paypal seems to be the best option (for non US Merchants).
I need to have
Ability to accommodate monthly and annual billing
Ability to suspend, cancel accounts etc
Deal with out-of-date card details or failed payment
just as mentioned here:
Recurring billing with Rails - what are my options?
I've come across various Paypal solutions like:
** Express Checkout
** Website Payments Standard
and various implementation options like ActiveMerchant, paypal_recurring gem
Just wanted to know
[A] - which Paypal option is the best one for subscription based billing with conditions 1-3 above and below additional condition:
for non US merchants
[B] - what are the best implementation options as in ActiveMerchant, or the paypal_recurring gem?
I would recommend going with Express Checkout and Recurring Payments. Specifically, you'll be using SetExpressCheckout, GetExpressCheckoutDetails (optional), DoExpressCheckoutPayment (optional), and CreateRecurringPaymentsProfile depending on exactly what you're doing with your application.
SEC will return a token that you'll use to redirect the user to PayPal as well as in following API calls.
GECD is used to obtain buyer details (ie. shipping address, address status, payer status, etc.) from PayPal now that the user has signed in and agreed to continue.
DECP would allow you to finalize a one-time payment that includes shipping and tax info, item details etc.
CRPP allows you to setup the recurring profile including one-time initial payment, trial amounts, regular amounts and periods, etc.
Then behind that you can use the UpdateRecurringPaymentsProfile API to manage the profiles programatically.