Direct Carrier Billing - Is it worth Implementing - mobile

I have a Mobile website which sell Products, its built in Asp.net/C#. I am exploring the idea of adding a new Payment Method on my website which will allow customers to pay using their Carrier aka Direct Carrier billing.
I want to get opinion from folks who have Direct Carrier Billing implemented on their Mobile Website.
How well was it received by the Customers
How complex is it to implement such a payment method (is it worth implementing)
Lastly, has anyone implemented http://www.billtomobile.com/, are there any other options apart from billtomobile
Thanks!

I have experience developing wap premium billing in some countries (es, it, za, pt, etc), normally using big aggregators. Usually it´s very simple to develop. There are http APIs, and you have to redirect consumer to carrier billing page, and it returns to you with billing information. Normally consumer has to accept the payment in carrier payment page.
I think main problem it´s you only can bill in some APNs for example, you can´t bill to blackberries or opera mini consumers, so other APNs don´t support wap payments. For example, in spain there is a commercial APN called "internet connection". Of course, you can´t bill to wifi users.
I think in others countries like UK, wap payments are broadly accepted. I belive one option is to mix wap payment with SMS premium.

Related

Server Architecture for application that needs to have country code top level domain

I was working on an web and mobile application which was startup business of Australia. We have our linode server and database in Singapore. We have a separate codebase for web app and mobile app(APIs). The business worked pretty well and now the client wants to expand their service in USA too.
The web app was hosted as appname.com.au and now he wants to launch the Application in USA as appname.com. And he wants to utilize the same mobile application for both Australia and USA because of not enough funding.
The problem is there will be many additional features/modifications in business logic for USA.
My main concern is should I continue on single web app or make new app for USA.
Since, we already have two separate codebases i.e. one for existing web app and another for APIs => mobile app. Maintaining more codebases will be very difficult for us.
The products that is sold via app should be location aware i.e. as popular products for one state of USA from another or from Australia will obviously vary, features product in home page should vary too.
The products uploaded to the Australia can be seen by the users of USA but, shouldn't be able to buy and vice-versa.
For this, should we continue to work on the same app or go with the new separate app for USA. Chances are this application will grow hugely in coming days and we need to scale it more thus, we are pretty stuck on what's the right/better thing to do.
Any help will be highly appreciated. If you don't understand it clearly I will let you know via comments. And yeah thanks for your time :)

Parallel Payment through mobile native app

I am trying to find a parallel payment implementation for my mobile app, where the payment should happen with in my application and not redirected to any browser.
I have seen few options like paypal parallel payment, but this doesn't provide native app purchase support.
Can some one please point me to right direction. I am wondering am I only one trying for this option? :)
Your help is greatly appreciated.
Thanks,
Ramesh.V
You are looking for an API payment gateway rather than a checkout page solution. There are numerous services such as Stripe, BrainTree, BlueSnap and even PayPal that offer this.
The reason this is not popular for apps is that you'll need to become PCI compliant for that, which is a pain. Non of the above services will grant you access to the API without it, but they will be happy to give you a checkout page (browser) to drop the PCI compliance requirement.
I've successfully used a service called Zooz for my mobile checkout and it works nicely.
You can goto www.zwitch.co . This is an Indian payment startup which offers in-app payment natively.They have mobile SDK with which you can accept payments in your app.You can design your own payment page.They say you will be reduced from the PCI Scope

Paypal payments standard with mobile optimized checkout

I am running a Django app that is hooked up to paypal payments standard and that generates encrypted 'Buy Now' buttons. Everything works as it should on desktop, but when I use a mobile device (android and IOS), I do not get sent to the mobile optimized checkout page.
If I go to this non-encrypted test page, I actually get the mobile checkout page. As soon as I change that fake business email to my real one, I only get the desktop page.
This leads me to believe I have some kind of configuration issues in my merchant account, as opposed to an issue with encrypted buttons.
I looked at the documentation on x.com. They mention that the mobile checkout page is not compatible with these use cases:
Instant Update API
Buyer Supplied Price, Desc, Qty
Profile Based Shipping & Tax Discounts
Payment Type: Auth, Order
Inventory Management
I originally had shipping rules, so I deleted those. I don't think I have any of the other things enabled, but its hard to tell seeing as these unsupported use cases are really vague. I've also read this SO post, and I have disabled my tax rules, but it did not fix the issue for me.
Does anyone have experience with this? Is there a way to force the mobile version of the checkout page, using paypal payments standard?
I "fixed" this by implementing their Express Checkout flow.
Don't believe their documentation. Express Checkout can do EXACTLY what paypal payments standard can do, and the API has nice features like forcing the non-paypal account pane to open by default.

Direct Carrier Billing providers

I have been doing some research on payment providers for in-app billing that support direct carrier billing in USA. So far I have found that Google Play support for carriers AT&T, Sprint, and T-Mobile. And WAC support AT&T.
Anyone have been working with or know of any other payment providers?
Conditions:
Support carrier billing in USA
Do not use Premium SMS
And support more than one carrier.
I'd suggest http://bango.com/mobilebillingcoverage/
JunglePay.
See also: http://www.quora.com/Michael-Whel/answers

best cross-platform mobile payment gateway/provider (Android, iPhone, WebOS etc.)

Which is the best cross-platform mobile payment solution?
I did work with Premium SMS gateways before, but premium sms is a bit tedious for customers in my opinion. If a customer wants to pay he needs to enter his phone number, then he receives some unique ID he has to enter into a form again for finalizing the payment.
So I wonder, if there are mobile payment providers offering something which is easy to use for customers, like in-app-payment, but cross-platform (iPhone, WebOS, Android etc.).
Best
Milanko
For my mobile repair buisness i use pay anywhere app available for the android and iphone. Its completely free and you recieve a card reader that plugs directly into your device. The app and card reader are both free, they only charge a small fee per transaction. (1% per transaction) not too bad in my business!

Resources