I feel like this should be possible and even common but haven't come across it in the documentation or on SO yet.
I sell a B2B subscription, and the norm in the industry is to send an invoice to the business to be paid by the accounting department. In many cases, the company is paying for access to the platform for multiple employees.
I'd like to pass an array of customers for a single subscription, so that when the subscription expires, all users lose access (or renew) in the following year. Is this possible?
No, this is not supported. Stripe is an abstraction for payments that you'll need to model appropriately for your business. In this case, your "Customer" could be the company, with the accounting representative as the billing contact. Then in your system you'd map individual user accounts to that customer/company account to grant or deny access to the service or features.
You do not need to (and should not) create a Stripe Customer for each individual employee at the company accessing your service if that does not fit the payments model for your business.
Related
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.
My original plan for the iOS app I'm developing was to make it free for all users except for administrators of "organizations" stored in a cloud database. These administrators pay a monthly subscription fee to maintain these organizations, and free users join them. An organization's administrator is the only one who can accept new users and set user permissions.
However, I realized that I have no way to check whether an administrator's subscription has expired from the point of view of another users, meaning it may be possible for an administrator to get a free trial, set up an organization, join it from an alternate account, set up permissions, cancel the subscription, and continue using the app as normal without paying. Currently, the only case that the app can handle is if the administrator tries to log into an organization after the subscription has expired.
I planned to avoid this issue by having "active" and "inactive" states for organizations stored in the database, but I still need a way for the app to recognize that a subscription has expired and deactivate the organizations associated with the user in question. I'm not sure how to do this, other than from the point of view of the admin, who could simply stop using the account before the subscription expires, and/or delegate management of an alternate, non-admin account to someone else.
I also realized that this specific setup might violate Apple's policy on in-app purchases, since I am effectively indirectly taking functionality away from free users due to paid users' subscriptions expiring. If this is the case, I'll have to rethink the payment structure of my app entirely. Am I allowed to handle subscriptions this way? If so, how can I a) reliably ensure that my app disables an organization when its admin's subscription runs out, or b) check whether an admin's subscription has run out when another user in the organization tries to log in?
I've looked at stripe connect and it forces each user to impute their Social Security number and etc. just so they accept payments for a item they want to sell.
Is there a less painless method where users can sell something on my site, receive monies, and buy from other users?
I tried using stripe alone and it pays me directly. Problem is I want user to sign up, sell something on the site, and get paid. I'm not sure how this can be done without having each user impute social security numbers, tax id, and other personal information if all they want to sell is a pen.
For financial compliance reasons (know your customer laws, anti-money laundering stuff), as well as protecting you from chargebacks and refunds, you'd have to use Stripe Connect and either Standalone or Managed Accounts. Unfortunately this means you'll have to collect certain information from the user like their bank account, date of birth, last 4 of their social, etc.
You can using their Transfers API, but you need to be in the US and so do they. https://stripe.com/blog/send-payouts-with-stripe
It is known that PayPal supports Adaptive(Chained) payments where one buyer sends the money and it is processed using one API account holder and the money can be sent to multiple
users.
My question is,
Does this approach also supports
accepting credit card (for the
buyer)?
Is it possible to capture the card
details at our website and use the
API (in the backend) without
redirecting to PayPal website
itself?
Here is my requirement...
I am running a website where sellers can sell their products and buyers buy them.
Seller sets the price and i get a commission
Eg. Person A sells Product P for $100. (My commission is 2%)
Person B buys P. and makes the payment in my website itself. Using Paypal API, i want to process B's credit card and charge him $100. Get my share of $2 and send rest of $98 to Person A.
thanks in advance,
Kannan R
Q1. YES it is possible to accept credit cards (PapPal Adaptive payments supports Guest Payments... where the user can enter their credit card details.
Q2. YES. In continuation of answer to Q1, the credit card details entered acts as the explicitly approved payment hence no need to redirect the sender to Paypal website for authorization.
http://www.paypal-labs.com/TechDocs/
This link explains things better, check out for the Guest Payments link..
Hope it helps.
rgds,
Sourcebits Team.
For Question #2:
While it is possible to capture the credit card details on your site, you should be aware that there is something called PCI Compliance, which is basically a set of rules you need to follow to ensure that your server and your software is secure.
It is not easy to meet PCI requirements on your own (time, consultant costs, regular inspections, understanding the rules etc.). And if the rules are violated or your server is hacked you could be fined hundreds of dollars/rupees per "lost" credit card details.
Search SO for some good information about this
I would like to know if there is a possibility of transferring money from my sellers customer to my seller directly without me getting involved?
Setup is like this
I've my website
Sellers register and sell their items
Customers register and buy sellers items..
What i want is to take money from customers account (be it credit card / debit card) and transfer directly to sellers account. Simply money shouldn't be deposited into my account and then transfer to the sellers.
I am using Ruby on Rails to build the application. Any payment gateway which supports this?
rgds,
Kannan R.
Looks like you want to transfer money from account to account (RTGS / Visa)... If that is the case, i don't think Payment gateways support that.
If you want to have a setup like this,
each of your sellers have their own payment gateway account (like authorize.net / paypal / etc) then you can use their account credentials to use the corresponding API and take money directly into their account from the customers
In which case you are not involved in the payment (though you are providing the service).
If you are not restricting your sellers to use a set of payment gateways... then you'll have to implement the logic of which seller using which payment gateway, use the corresponding credentials, and use the corresponding API, etc which i believe is a huge task !!!Congrats with that