Payment with corona?

[pabloapdz]

Good morning / afternoon / evening,

I was searching the internet and could not find information on whether Corona allows me to make payments through the app.

The only basic information I could find was a paid plugin in Corona Marketplace that refers to payments via Paypal.

And then looking for some more I found in the forum of the crown itself (this), but to my understanding after reading the topic, that this refers to purchases directly with google play, that is, opening “that famous GP window” …

I was thinking of something more concrete, I wanted to be able to realize sales within my application so that people could simply pay with the credit card or even with some virtual wallet. (As if it were the famous apps, Ifood, Rappi, Uber, 99 …)

Can anyone tell me if the corona allows me to make sales in the app through only card numbers ( OR NUMBER OF VIRTUAL WALLET ) ?

Note : Even if it is necessary to have a business account no problem, I have a bank account and I have CNPJ as well.

Note 2 : CNPJ is the National Registry of Legal Entities

[sporkfin]

This seems like more of a server-side / back-end question.  If you have a payment system set up in PHP / MySQL (or something else) then I would think a Corona app could be your front in conduit that accepts payments.

[roaminggamer]

Are you trying to make a POS (Point Of Sale) system?  A catalog?  A menu for restaurant(s).  What?

As far as the question, “Can one write an app (using Corona) that will allow the user to make a purchase using a credit card and/or Paypal and/or some other system?”  Yes.  This is possible and many of us have done so.

However, will need some kind of server back end, be it your own, or one controlled by the payment service.

I’ve used Stripe and I’m sure others have used PayPal services in apps.

When I used Stripe I talked a intermediate back-end server, but I believe there is a plugin which lets you talk directly to the Stripe servers, which may simplify things for you.

https://marketplace.coronalabs.com/corona-plugins/stripe

https://marketplace.coronalabs.com/corona-plugins/paypal-plugin

Can you tells us ‘exactly’ what you want to make?  Otherwise it hard to give you advice.  Give us your elevator pitch.

[pabloapdz]

Thank you both for the answers.

Well, sorry for the delay, there were some setbacks yesterday that could not be answered right away.

Hmmmm, I quite understand how it works, I’ll be taking a closer look at it.

@Roaminggamer

I’m trying to develop an application that will be able to buy custom items, but not only this, taking a look at the games already created, an example that would fit the best would be Counter Strike.

There are several and several weapon skins in it, but some skins are extremely rare, which ends up creating a “market” out of the game on the skins; Whoever owns such a skin can sell it for a price he wants.

Note: I know that the “@ + name” does not mention the person in the topic, but is only to facilitate understanding of the response

[roaminggamer]

You want to create a marketplace for items in your game and have people buy those items via CC and/or PayPal and/or other non-IAP?

That will probably not be allowed by Apple (and probably Google Play too).

If you want to sell in-game items, you need to use IAP purchases.

If you have a lot of items, you can have a in-game store that uses in-game currency, but that currency needs to be earned in-game and/or bought via IAP.

As far as allowing players to sell items for $.  Again, I don’t think that will be allowed.

Apple is very strict about this kind of thing.  They don’t want to be cut out as the middle-man for $$$$.  

You might want to give the Apple developer guidelines a thorough read before investing too much effort in this.

[rob]

Side note on the @ tagging. This dated back to the early days of the Internet, and perhaps even earlier. Twitter, of course, made it popular.

Most people came up with name tags instead of their real name. An old Bulletin Board system, may have you use a single word, 8 character max nickname.  Let’s say mine is/was SuperRob. First, in no way, does that mean my name is Rob. I could be Robert, Bob, Bobbie, Bert or half a dozen names. It might not even be my first name. Calling me “Super” makes little sense either, but that’s my own line persona. Since things like “super” or “roaming” are regular words that could be used in regular text, so the idea of @tagging names became a clear way to refer to someone in the middle of a text block. For instance no one here know’s your real name, and I can’t reasonably determine what to call you, so you’re going to be referred to as @pabloapdz. There is a  good chance you would be okay being referred to as Pablo. So we use the @name standard when referring to a person in a post, unless it’s clear what to call someone from how they reply. For instance, you can safely call me Rob because that’s how I end my messages.

Rob

[richard11]

Just wanted to throw my 50c into this as a web developer specialising in e-commerce

Firstly, if you implement a direct payment mechanism that doesn’t use the Apple/Google store IAP API, you’ll need a payment gateway such as Sagepay, Worldpay, Barclaycard, and so on. Payment gateways tend to charge a monthly fee of about $20 for about 500 transactions, and a per-transaction fee for anything that exceeds this. In other words, given the relatively small amount that the average microtransaction is worth and the presumably large number of transactions you’re hoping to receive, doing it yourself isn’t likely to be any cheaper than using the store API.

Secondly, as already stated, implementing a gateway like this would require a server side development that acts as middleman between your app and the payment gateway, which is already middleman between merchant and customer banks. Seems a bit overkill to me, and a considerable development compared to just implementing the store-provided IAP mechanism.

Thirdly, if you do implement a payment gateway as middleman, leaving your app to talk to your own server, you’ll effectively need to handle the customers card details directly. I.e. their entered details will be passing through your app, to your server, and on to the gateway. This kind of handling requires the highest level PCI-DSS compliance which is both expensive and frankly, a pain in the butt to adhere to. You’d need to implement things like perimeter CCTV and legitimate security protocols so that only staff who actually need access to this information have it, and then pay for regular compliance tests. Absolutely not worth the hassle when Apple and Google already provide a simpler mechanism and act as payment processors for you.

And finally, as a user, if I clicked in to an IAP item within a mobile app and it asked me to enter card details without going through the official store provided mechanism, I’d be uninstalling that app immediately. That just wouldn’t seem trustworthy at all!

[sporkfin]

This seems like more of a server-side / back-end question.  If you have a payment system set up in PHP / MySQL (or something else) then I would think a Corona app could be your front in conduit that accepts payments.

[roaminggamer]

Are you trying to make a POS (Point Of Sale) system?  A catalog?  A menu for restaurant(s).  What?

As far as the question, “Can one write an app (using Corona) that will allow the user to make a purchase using a credit card and/or Paypal and/or some other system?”  Yes.  This is possible and many of us have done so.

However, will need some kind of server back end, be it your own, or one controlled by the payment service.

I’ve used Stripe and I’m sure others have used PayPal services in apps.

When I used Stripe I talked a intermediate back-end server, but I believe there is a plugin which lets you talk directly to the Stripe servers, which may simplify things for you.

https://marketplace.coronalabs.com/corona-plugins/stripe

https://marketplace.coronalabs.com/corona-plugins/paypal-plugin

Can you tells us ‘exactly’ what you want to make?  Otherwise it hard to give you advice.  Give us your elevator pitch.

[pabloapdz]

Thank you both for the answers.

Well, sorry for the delay, there were some setbacks yesterday that could not be answered right away.

Hmmmm, I quite understand how it works, I’ll be taking a closer look at it.

@Roaminggamer

I’m trying to develop an application that will be able to buy custom items, but not only this, taking a look at the games already created, an example that would fit the best would be Counter Strike.

There are several and several weapon skins in it, but some skins are extremely rare, which ends up creating a “market” out of the game on the skins; Whoever owns such a skin can sell it for a price he wants.

Note: I know that the “@ + name” does not mention the person in the topic, but is only to facilitate understanding of the response

[roaminggamer]

You want to create a marketplace for items in your game and have people buy those items via CC and/or PayPal and/or other non-IAP?

That will probably not be allowed by Apple (and probably Google Play too).

If you want to sell in-game items, you need to use IAP purchases.

If you have a lot of items, you can have a in-game store that uses in-game currency, but that currency needs to be earned in-game and/or bought via IAP.

As far as allowing players to sell items for $.  Again, I don’t think that will be allowed.

Apple is very strict about this kind of thing.  They don’t want to be cut out as the middle-man for $$$$.  

You might want to give the Apple developer guidelines a thorough read before investing too much effort in this.

[rob]

Side note on the @ tagging. This dated back to the early days of the Internet, and perhaps even earlier. Twitter, of course, made it popular.

Most people came up with name tags instead of their real name. An old Bulletin Board system, may have you use a single word, 8 character max nickname.  Let’s say mine is/was SuperRob. First, in no way, does that mean my name is Rob. I could be Robert, Bob, Bobbie, Bert or half a dozen names. It might not even be my first name. Calling me “Super” makes little sense either, but that’s my own line persona. Since things like “super” or “roaming” are regular words that could be used in regular text, so the idea of @tagging names became a clear way to refer to someone in the middle of a text block. For instance no one here know’s your real name, and I can’t reasonably determine what to call you, so you’re going to be referred to as @pabloapdz. There is a  good chance you would be okay being referred to as Pablo. So we use the @name standard when referring to a person in a post, unless it’s clear what to call someone from how they reply. For instance, you can safely call me Rob because that’s how I end my messages.

Rob

[richard11]

Just wanted to throw my 50c into this as a web developer specialising in e-commerce

Firstly, if you implement a direct payment mechanism that doesn’t use the Apple/Google store IAP API, you’ll need a payment gateway such as Sagepay, Worldpay, Barclaycard, and so on. Payment gateways tend to charge a monthly fee of about $20 for about 500 transactions, and a per-transaction fee for anything that exceeds this. In other words, given the relatively small amount that the average microtransaction is worth and the presumably large number of transactions you’re hoping to receive, doing it yourself isn’t likely to be any cheaper than using the store API.

Secondly, as already stated, implementing a gateway like this would require a server side development that acts as middleman between your app and the payment gateway, which is already middleman between merchant and customer banks. Seems a bit overkill to me, and a considerable development compared to just implementing the store-provided IAP mechanism.

Thirdly, if you do implement a payment gateway as middleman, leaving your app to talk to your own server, you’ll effectively need to handle the customers card details directly. I.e. their entered details will be passing through your app, to your server, and on to the gateway. This kind of handling requires the highest level PCI-DSS compliance which is both expensive and frankly, a pain in the butt to adhere to. You’d need to implement things like perimeter CCTV and legitimate security protocols so that only staff who actually need access to this information have it, and then pay for regular compliance tests. Absolutely not worth the hassle when Apple and Google already provide a simpler mechanism and act as payment processors for you.

And finally, as a user, if I clicked in to an IAP item within a mobile app and it asked me to enter card details without going through the official store provided mechanism, I’d be uninstalling that app immediately. That just wouldn’t seem trustworthy at all!