we are developing a SaaS (node.js) and struggling how we could manage our subscriptions and billing. First idea was Stripe, but there are limitations like no PayPal Integration, not covering all tax rules in Europe etc.
Is there a solution in node so we could integrate it seamless in our product? something like:
- subscription management
- provides payment cia Stripe, PayPal, amazon Pay
- creates invoices
- compliant to european tax law (reverse charge etc)
Any idea? I asked google (and other engines;)), no result.. there are so many saas build up on node, can't imagine there's no solution
best
Felix
Related
I have an app with Free, Premium and Gold subscription plan. Based on the plan user can access features like filters, messages, likes.
Now, I'm planning to have an web app only for payments using stripe. So, users will directed to web app to pay payments.
Will apple allow this approach or will they insist to use in-app purchase?
I'm little confused here. Need your suggestion here?
This is a question for Apple Review team, you should reach out to them directly and clarify. Stripe doesn't replace in-app purchases and you need to use Apple's API to perform in-app purchases. See here for details
why do developers use Stripe not Master-card API or Visa API while stripe charges money more. i checked and found out Master-card and Visa have their own API's , i guess there's something there i don't understand? probably i live in egypt, which global service should i use to integrate in my PHP websites while Stripe is not available in egypt?
sjsonp1389885476573({
"error": {
"message": "Your card was declined.",
"type": "card_error",
"code": "card_declined"
}
}
, 402)
Thank you
One of the primary reason why developers use payment gateways such as stripe and not separate APIs for master, visa, maestro etc. as you need to do development and testing individually for these APIs along with monitoring any changes that happen with them.
Stripe on the other hand provides an API layer over all these APIs and simplify them so that businesses don't have to worry about integrating the separate APIs.
The list of payment gateways available in Egypt currently includes :
2Checkout
BitPay
Coinbase
GoCoin
Mastercard Payment Gateway Services
NETbilling
PayFort
PayPal Express Checkout
Paystack
Also, the integration time is very less with these payment gateways as compared to the APIs of payment solutions such as master, visa, maestro, etc. as these gateways provides single API which supports payment options for all major payment solutions.
Hope this helps!
I'm building an application for a new small business. They run events at race tracks, and the application is a registration system for said events. As a small business the owner doesn't want to worry about handling people's credit card info. They are just starting up and we are building from the ground up. So we are looking at using third party services like Google Wallet and PayPal.
So looking at the documentation, we have the Instant Buy API. Seeing as we aren't planning on taking direct credit card payments, it seems like a pain to setup payment processing through another service to use the Instant Buy. But we aren't selling a "Digital Good", as far as I can tell (I haven't seen a documented definition for this), so does that mean we can't use the API for Digital Goods? I haven't found any documentation that lays this out as a policy. It seems like it would be a lot simpler to implement, even with the cut Google takes.
There is a page at the google wallet documentation site called Which API Should I Use?, the first item there is:
The quick answer: it depends on your goals, your platform and what
kind of goods or services you're selling. The Instant Buy APIs are for
selling physical goods, while digital goods sellers should use the
Google Wallet for Digital Goods API for web apps or Google Play In-app
Billing for Android for native Android apps. To engage your customers
with offers and loyalty programs, use the Wallet Objects API.
Now, the Instant Buy APIs are for those business that have an existing payment gateway setup, but need to offer Google Wallet as a payment option.
In your situation, as you don't have a payment processor setup:
To sell physical goods on web apps and mobile apps that run on
browsers, use Instant Buy for web. You'll keep your existing payment
processor and optimize your payment flow with Google Wallet, just like
with Android. You can use Instant Buy for web to sell digital goods,
but if you lack a payment processor or resources to maintain and
develop a PCI-compliant online store, you should use the Google Wallet
for Digital Goods API.
In your experience which are the best recurring payment solution and merchant account providers in Asia?
What would you think are the key criteria to choose a recurring billing solutions provider? (with most Asian currencies)
Based on what I found in my search so far, I noted the following.
PayPal does provide recurring payment services in Asia - but customer support is as bad as it is elsewhere with PayPal around the world and with the additional risk of getting blocked for >5% of refunds.
PCI Compliance is absolutely necessary on the part of provider.
Based on initial search found "Money Bookers" but not sure how good their service is - seem to be able to transact in 200 countries so far.
Your experiences (good experiences & warnings) in dealing with recurring billing providers and merchant accounts will be helpful to choose for my implementation.
TechCrunch recently featured SaaSy which seems to fit your criteria pretty well: http://techcrunch.com/2011/03/17/online-subscription-billing-is-still-a-hassle-saasy-aims-to-change-that/
I have a client who has content that he wants to publish on the web (and potentially for iPad). He wants the viewer to pay to subscribe for the content.
Is there a service out there I can integrate with to for handling the accounts and collecting the monthly subscription fee (using credit cards or something else)?
There are several services out there that can help you with this - Recurly (where I work), Chargify, CheddarGetter, Spreedly, etc. These services handle the recurring billing aspect, customer management, email communication, following up with failed payments, etc. You'll also need a payment gateway (to process the cards) and a merchant account (for the payment gateway to deposit the funds into).
Authorize.net and PayPal both have recurring billing features, but the logic for upgrading/downgrading accounts is not there or difficult to use, and you'll still need to handle customer communication for failed payments and other actions.
You need to use a payment gateway here, which will be responsible for handling the transaction between your site and the many different payment networks. There are a lot of operations happening in between, so you might want to check out the wikipedia article for a step by step information on that.
We personally use authorize.net in our company for many of its advantages, some of which are:
It has an API that makes it easy to integrate with any language.
It is a trusted brand already, proven by the number of merchants that use them.
It is secure.
It provides the service with a reasonable price.
Most of major payment gateway providers do support recurring billing or subscription plans, paypal,authorize.net etc, most of the time you have to log in to your account admin console and configure a plan, and send the payment plan id with the payment request to the payment gateway. some payment gateway providers, like Braintree supports to create recurring billing plans dynamically and assign users to that plan at the run time it self, how ever it's always better to go for a local payment gateway provider or a payment gateway which provides low fees, if your preferred payment gateway provider is not supporting recurring billing anther options is to store cc details on the server and and handle it your self but it's a great risk to store cc details on the server, and you will have to follow PCI standards and it's hard.