Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×
Google Businesses The Almighty Buck The Internet

Google CEO Confirms Online Payment System 251

didde writes "Reuters is reporting on statements that Google's CEO Eric Schmidt had made regarding Google's upcoming payment system. Apparently they're not looking to compete with PayPal." From the article: "Schmidt said Google does not intend to offer a 'person-to-person stored-value payments system' like PayPal's, in which money briefly resides in PayPal's control during the transaction, but he did not give details of how the Google system would differ."
This discussion has been archived. No new comments can be posted.

Google CEO Confirms Online Payment System

Comments Filter:
  • Good Riddance! (Score:2, Informative)

    by Windsinger ( 889841 ) <phox@DALIoptonline.net minus painter> on Thursday June 23, 2005 @11:04AM (#12889490) Homepage
    Can't wait. Can't wait to drop Paypal and their horrible transaction fees.

    I guess what aggrivates me more is "Not being allowed to post buyer pays paypal transaction fees on ebay purchases" in your ebay posts.

    And all the other crap Paypal pulls out of it's mighty ass.

    Semi-intersting links:

    http://paypalsucks.com/ [paypalsucks.com]
    http://www.paypalwarning.com/ [paypalwarning.com]
  • Global coverage? (Score:5, Informative)

    by kkumer ( 36175 ) on Thursday June 23, 2005 @11:10AM (#12889554) Homepage
    Well, one improvement over PayPal would be global coverage. Just few days ago I was very impressed by a nice piece of software (mp3splt [sourceforge.net], BTW), and I decided to donate some money to the corresponding Sourceforge project via PayPal. Half way through I found out that my small European country (Croatia), was not covered by PayPal services.
  • Re:Good Riddance! (Score:2, Informative)

    by AuSerpent ( 5434 ) * on Thursday June 23, 2005 @11:12AM (#12889574)
    Bidpay is fairly popular in the ebay crowd and the buyer pays the transaction fee there.

    That said, in most every business that accepts credit card the seller pays the transaction fee and covers it by adjusting the price of the item.
  • by Otto ( 17870 ) on Thursday June 23, 2005 @11:53AM (#12890178) Homepage Journal
    Converting real cash into fake cash gives the fake cash a real value and thus makes it into real cash.

    In other words, if I buy a Gbuck and send it to a friend and they convert it back to whatever it is worth in cash, how is this any different than what paypal does, realistically?

    If they create their own currency and decide not to tie it in a fixed way to another currency, then that's interesting, but doesn't change the fact that it's still them accepting one currency for a temporary period of time.

    It also introduces the problem of fluctations of the new currency. People buy Gbucks, wait for them to be worth more real bucks, then cash out. Google is now out a ton of real cash. This is done with real cash all the time, but making it easy to convert between currencies will make this simpler. Only way to combat this that I can see is for google to implement a conversion fee to stabilize the fluctuations, which will discourage the currency from taking off in the first place.
  • by amaiman ( 103647 ) on Thursday June 23, 2005 @12:59PM (#12891178) Homepage
    Your post advocates a

    (*) technical ( ) legislative (*) market-based ( ) vigilante

    approach to fighting spam. Your idea will not work. Here is why it won't work. (One or more of the following may apply to your particular idea, and it may have other flaws which used to vary from state to state before a bad federal law was passed.)

    ( ) Spammers can easily use it to harvest email addresses
    (*) Mailing lists and other legitimate email uses would be affected
    ( ) No one will be able to find the guy or collect the money
    ( ) It is defenseless against brute force attacks
    ( ) It will stop spam for two weeks and then we'll be stuck with it
    (*) Users of email will not put up with it
    ( ) Microsoft will not put up with it
    ( ) The police will not put up with it
    ( ) Requires too much cooperation from spammers
    (*) Requires immediate total cooperation from everybody at once
    (*) Many email users cannot afford to lose business or alienate potential employers
    ( ) Spammers don't care about invalid addresses in their lists
    ( ) Anyone could anonymously destroy anyone else's career or business

    Specifically, your plan fails to account for

    ( ) Laws expressly prohibiting it
    ( ) Lack of centrally controlling authority for email
    ( ) Open relays in foreign countries
    ( ) Ease of searching tiny alphanumeric address space of all email addresses
    ( ) Asshats
    (*) Jurisdictional problems
    ( ) Unpopularity of weird new taxes
    ( ) Public reluctance to accept weird new forms of money
    ( ) Huge existing software investment in SMTP
    ( ) Susceptibility of protocols other than SMTP to attack
    ( ) Willingness of users to install OS patches received by email
    ( ) Armies of worm riddled broadband-connected Windows boxes
    ( ) Eternal arms race involved in all filtering approaches
    (*) Extreme profitability of spam
    (*) Joe jobs and/or identity theft
    ( ) Technically illiterate politicians
    ( ) Extreme stupidity on the part of people who do business with spammers
    ( ) Dishonesty on the part of spammers themselves
    ( ) Bandwidth costs that are unaffected by client filtering
    ( ) Outlook

    and the following philosophical objections may also apply:

    (*) Ideas similar to yours are easy to come up with, yet none have ever been shown practical
    ( ) Any scheme based on opt-out is unacceptable
    ( ) SMTP headers should not be the subject of legislation
    ( ) Blacklists suck
    ( ) Whitelists suck
    ( ) We should be able to talk about Viagra without being censored
    ( ) Countermeasures should not involve wire fraud or credit card fraud
    ( ) Countermeasures should not involve sabotage of public networks
    ( ) Countermeasures must work if phased in gradually
    (*) Sending email should be free
    ( ) Why should we have to trust you and your servers?
    ( ) Incompatiblity with open source or open source licenses
    ( ) Feel-good measures do nothing to solve the problem
    ( ) Temporary/one-time email addresses are cumbersome
    ( ) I don't want the government reading my email
    ( ) Killing them that way is not slow and painful enough

    Furthermore, this is what I think about you:

    (*) Sorry dude, but I don't think it would work.
    ( ) This is a stupid idea, and you're a stupid person for suggesting it.
    ( ) Nice try, assh0le! I'm going to find out where you live and burn your
    house down!
  • by Michael Spencer Jr. ( 39538 ) * <spam@mspenc e r . n et> on Thursday June 23, 2005 @08:20PM (#12896086) Homepage
    (Disclaimer: I work for a payment processing company, First National Merchant Solutions, so the fees you're advocating against are what keep me fed and pay my bills. I'm naturally biased toward a system that keeps me employed, but I have other interesting insights into payment processing which people outside this industry might not have.)

    There's one important component of payment processing you're missing. If it weren't for this component you would be completely correct, so I'm pretty sure I've identified the part you're missing.

    Sometimes things go badly, and some kind of fraud protection is needed. That fraud protection costs much more money than the account-to-account transfers you're talking about.

    Suppose in one scenario, both parties to the funds transfer trust each other completely, and both sides waive any right to fraud protection. One person can put cash directly in the other's hand, or they can do a free bank transfer. Nothing complicated can happen here, so no extra effort can be expended, so no fees are needed.

    In scenario two, suppose the two parties to the funds transfer have a buyer/seller relationship, and the validity of the transfer depends on material properties of that buyer/seller relationship. Think Visa/Mastercard chargeback rights (which are familiar and comfortable to me, so I prefer them as an example). If something goes wrong with the sale, the transfer of funds needs to be reversed. But who can decide if something went wrong with the sale? Who is telling the truth? Maybe the customer is claiming they never received mail-order merchandise, but they actually do have it and are lying? Maybe the customer is claiming they never received mail-order merchandise because the seller never sent it? Maybe something different happened?

    Do we really want to require the buyer to take the seller to court to get their money back? (Sure, some merchants are small mom and pops, but some are the size of Gateway, the Gap, LL Bean, etc. Their purse is longer than yours or mine.)

    According to my (biased) view of the world, when a merchant runs sales they must pay transaction fees. When they ask me what their fees pay for, here's what I see:

    * Some fees are 'interchange' and 'assessments', which go straight to Visa/Mastercard, for their operational costs, and to the banks which issue those cards, for profit. I don't work on the card-issuing side so I don't know. I guess this goes to pay for bank profit, for those rewards points customers get, and to offset the occasional customer bankrupcy or other bank write-off when a customer doesn't pay for the charges they make.
    * Some fees pay for the systems used to process those sales, both third-party systems (like Vital Processing Service, vitalps.com) and our own systems. We're a bank, so our systems follow a rigorous (and slow and expensive) development process -- but they're well-designed. We're a bank, with *vastly* greater assets at stake than those companies you see in the news for getting hacked. Those systems aren't cheap to build or maintain. Then again, you're not going to be seeing First National on the news for getting hacked. We won't be pulling a Card System Intl or a DPI Merchant Services any time soon.
    * Some fees pay for risk management: if a merchant runs a bunch of fraudulent sales, and then jumps the border to Mexico before anything gets charged back, we have to cough up those funds and then try to collect from the merchant later. We need some money to offset that risk.
    * Some fees pay for general company costs: tech support staff, customer service, computer guys, auditors, finance people, building rent, etc.
    * Some fees pay for the transfer of funds from the processing company (us) to the merchant's own bank account. That bank transfer isn't free: the two or three days of interest generated goes toward the cost of transferring money. There's no way to say "this transfer is for credit cards, so give us part of the fee back" or "this transfer is for a ch

egrep -n '^[a-z].*\(' $ | sort -t':' +2.0

Working...