Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <h2>Instant Buy</h2> <p>Instant Buy allows users to use their stored payment data from Google Wallet to purchase items from a merchant, with the <em>merchant</em> handling the transaction through a payment processor of their choice.</p> <p>Basically, when the user submits an Instant Buy request, it will appear to your app as if they just filled in a normal order with a credit card number and everything. Google doesn't take a cut of the transaction, because Google doesn't process the payment. However, whatever payment processor you use will probably take a cut.</p> <h2>In-App Purchases</h2> <p>In-app Purchases allows merchants to have <em>Google</em> handle the transaction and process the payment for a digital good. In this case, Google does take a cut of the transaction because they handled the payment processing.</p> <p>As far as your app is concerned, you never see payment details - Google takes care of all of that. Your app just gets a notification that user X bought item Y, and then later on, Google gives you the proceeds from the transaction.</p> <h2>The bottom line...</h2> <p>If you already have a system for handling purchases and processing credit card transactions, you probably want Instant Buy. It will sit on top of your existing infrastructure (so you don't have to have duplicate code paths) and won't cost you any money beyond what you're already paying your payment processor. It also lets your users purchase any kind of goods (physical or digital), since all it's really doing is providing payment info, not payment processing.</p> <p>If you don't already have a system for handling transactions, and all you want to sell are digital goods, In-App Purchases may be simpler, since it handles all of the payment processing for you, and the cut Google takes is <a href="https://developers.google.com/commerce/wallet/digital/faq#faq-payments-01" rel="noreferrer">reasonably competitive</a>.</p> <h2>For your particular case:</h2> <p>Since it sounds like you don't already have a payment processor lined up, and you're not trying to sell physical goods, I'd suggest looking at the <strong>In-App Purchases API</strong>.</p> <p><em>[Full disclosure: I work for Google.]</em></p>
    singulars
    1. This table or related slice is empty.
    1. POGoogle Wallet Instant Buy versus Inapp
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAmber
    1. USAmber
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POGoogle Wallet Instant Buy versus Inapp
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThank you, that was very helpful. =)
      singulars
      1. PO
      1. USKai
    2. COIn-App Purchases are only available to developers from certain countries, see: https://developers.google.com/commerce/wallet/digital/faq
      singulars
      1. PO
      1. UShonzajde
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload