Automatically charge credit cards

[Shrek]

Hi Google

when an order comes in.. why does the Buyer have to login into the Merchant center and click on "Charge" button. why can't this step be automatic or make it a preference. 

what if i start getting Million orders a second ??! You don't expect me to login into Merchant center and click on the "Charge" button ... at the speed of Million Clicks per second, do you?

Thanks for clarifying your thoughts around it.

Let me know if this is a gap ... I don't mind opening a bug for tracking purposes.

Sriks

[Joel Leitch]

Hi Sriks,

The orders will automatically get charged for you; however, right now it is currently configured to wait ~45 minutes. Outside of documentation, what could we do to help reduce this confusion?

One solution, that would somewhat align with Android Developers, is to disable the Charge button in the Merchant center. Do you think that would help?

Thanks for the feedback,

Joel

[Srikanth Pagadala]

Hi Joel

How about showing a ticking count-down right where we have "charge" button in the merchant center with a note something like:

Gateway will charge buyer's cerdit card in 5 mins 10 seconds. (and continuously ticking down).

[Srikanth Pagadala]

Hi Joel

After talking to my customers (very non-technical folks), they suggested following:

When a transaction occurs, have Google Wallet send an email to the Seller (this is missing today), and in it mention something like this : "Google Wallet will charge buyer's credit card in approximately 45mins (or say 10.33 PM PST). If you want to process the order immediately, please log into the Merchant center and press "Charge now" button.

something along these lines... you get the idea, don't you?

thanks

[Ed Chavez]

Hi Joel,

Just "dropping in" on this thread...

A bit confused - none of my sandbox (granted they are sandbox) testing exhibits this "charge button" behavior (In App Payments), is this ~45 min wait only in production?

This is pretty much how its been since (sandbox screenshot):

Seems this needs clarification...it changes "paid" (and the order flow for In App)....

Thanks!

Ed

[Joel Leitch]

Hi Ed,

I failed to mention in the previous post that this is a very recent change that was rolled out only a few days ago. Prior to the that release, the charge delay was set at a minute. This new behaviour affects both sandbox and production.

Here is a link that describes authorizations: http://support.google.com/wallet/bin/answer.py?hl=en&answer=105940. In short, an authorization is essentially a mechanism to guarantee that the funds are available.

Happy coding,

Joel

[Ed Chavez]

Hi Joel - 

Thanks!

Feedback (apologies if these were covered @last Hangout):

• Sounds confusing - I'm used to this only in the Google Checkout world (charge button - which can also be set to "auto-charge"), which makes sense because of the nature of what Google Checkout is used for (shipped products and/or services, including digital as well)
       
• Perhaps that's why I have  a confused reaction - in the GC world, the concept of "charge" is critical - you have to in order to get "paid"  - whether via API command or through the Merchant interface (an action must be done by the merchant).
• seeing this button "enabled" for In App is, well, strange - no idea why the 45 min delay was implemented, and perhaps that deserves its own thread, but if it doesn't really change the (original) In App flow, then the App seller flow shouldn't either... I guess the UI shouldn't give the impression (of change, needed action) either....
• if I'm guaranteed to be paid because of the (pre)authorization (meaning it will never return false/can't charge), then the charge button is somewhat unnecessary...
  
• however, if there is a chance that the subsequent charge of the (pre)authorization can fail, then the flow changes...dramatically - and would probably mean more changes coming to the API (again coming from the GC world, "notifications").
  

Thanks again...

Ed

On Saturday, May 12, 2012 3:24:42 PM UTC-7, jleitch wrote:

Hi Ed,

I failed to mention in the previous post that this is a very recent change that was rolled out only a few days ago. Prior to the that release, the charge delay was set at a minute. This new behaviour affects both sandbox and production.

Here is a link that describes authorizations: http://support.google.com/wallet/bin/answer.py?hl=en&answer=105940. In short, an authorization is essentially a mechanism to guarantee that the funds are available.

Happy coding,

Joel