Callback features

Hello,

We are developing a new web site which will basically be an
"indirect
sales channel" for multiple sellers. Our web site will
contain product
information from multiple sellers. Customers will be able to
click a
"Buy Now" button for any product. Each product's
Buy Now button will
be dynamically generated to have the appropriate code and
merchant
number for the particular seller of that product.

So when the customer clicks Buy Now, it will take them to
Google
Checkout, and at that point they will complete the sale with
that
specific seller. (There is no shopping cart, so one
transaction will
only involve one buyer, one product, and one seller at a
time - not
multiple products from multiple sellers).

So far using Google Checkout is no problem, but we would
like to get a
notification back from Google Checkout to our site, when the
sale is
finished. We are having some problems understanding which
parts of the
Google API to use.

1) If we use level_2 integration then various notification
options are
possible, but each seller would have to give us their
sensitive
information like bank account # etc., which we want to
avoid. We want
them to only give us their merchant number so that we can
create their
Buy Now butotn.

2) If we use the approach mentioned under "third party
tracking", then
we need to apply to be listed under Google's list of trusted
third
party vendors, and we are an early-stage startup, so that
seems
problematic.

Are there any other options?

Thanks for your help/advice,

Andrew


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "API Integration Basics" group.
To post to this group, send email to
google-checkout-api-integrationgooglegroups.com
To unsubscribe from this group, send email to
google-checkout-api-integration-unsubscribegooglegroups.com
For more options, visit this group at http://groups.google.com/group/google-checko
ut-api-integration?hl=en
-~----------~----~----~----~------~----~------~--~---

On Monday 11 June 2007 5:12 pm, BunsenHoneydew wrote:
> Hello,
>
> We are developing a new web site which will basically
be an "indirect
> sales channel" for multiple sellers. Our web site
will contain product
> information from multiple sellers. Customers will be
able to click a
> "Buy Now" button for any product. Each
product's Buy Now button will
> be dynamically generated to have the appropriate code
and merchant
> number for the particular seller of that product.
>
> So when the customer clicks Buy Now, it will take them
to Google
> Checkout, and at that point they will complete the sale
with that
> specific seller. (There is no shopping cart, so one
transaction will
> only involve one buyer, one product, and one seller at
a time - not
> multiple products from multiple sellers).
>
> So far using Google Checkout is no problem, but we
would like to get a
> notification back from Google Checkout to our site,
when the sale is
> finished. We are having some problems understanding
which parts of the
> Google API to use.
>
> 1) If we use level_2 integration then various
notification options are
> possible, but each seller would have to give us their
sensitive
> information like bank account # etc., which we want to
avoid. We want
> them to only give us their merchant number so that we
can create their
> Buy Now butotn.

You could use level 2 Notification without intruding on the
Merchant. 

You would need their Merchant ID and Merchant Key to build
the button 
correctly, using encrypted xml. You could include a
reference to your 
Merchant in the merchant-private-data which can go into the
enrcrypted string

The merchant would have to place the URL to your callback
script in the 
Merchant Center under Settings->Integration to make the
Notification API 
work. 

When a sale is initiated, the callback script would receive

the 'new-order-notification' xml stream which contains the
item(s) being 
sold, tax, shipping and address details, the buyer's Google
ID and the 
merchant-private-data which could contain the Merchant's ID
or a reference to 
a record containing the info you need to identify the
Merchant. 

The callback script could be the same one for all your
Merchants. No one else 
would be able to use it because only known Merchant ID/Key
combinations can 
access it.

Because you know from the outset which Merchant's goods are
being sold from 
within the callback script, you could provide bespoke
responses tailored to 
the Merchant's needs, as defined somewhere eg in a
database.

Google's callback system is the most complex I've run across
but also the most 
secure.

>
> 2) If we use the approach mentioned under "third
party tracking", then
> we need to apply to be listed under Google's list of
trusted third
> party vendors, and we are an early-stage startup, so
that seems
> problematic.
>
> Are there any other options?
>
> Thanks for your help/advice,
>
> Andrew
>
>
> 
-- 
--------------------------------------------------
Bob Hutchinson
Arwystli Networks
  Linux specialists
  Server administration
  Programming
  Web Hosting
  Mail Hosting
web: http://midwales.com
email: hutcharwystli.net
skype: bobhutch
--------------------------------------------------

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "API Integration Basics" group.
To post to this group, send email to
google-checkout-api-integrationgooglegroups.com
To unsubscribe from this group, send email to
google-checkout-api-integration-unsubscribegooglegroups.com
For more options, visit this group at http://groups.google.com/group/google-checko
ut-api-integration?hl=en
-~----------~----~----~----~------~----~------~--~---

This is very helpful. Thank you!
Andrew

On Jun 11, 2:12 pm, Bob Hutchinson <h...arwystli.net> wrote:
> On Monday 11 June 2007 5:12 pm, BunsenHoneydew wrote:
>
>
>
>
>
> > Hello,
>
> > We are developing a new web site which will
basically be an "indirect
> > sales channel" for multiple sellers. Our web
site will contain product
> > information from multiple sellers. Customers will
be able to click a
> > "Buy Now" button for any product. Each
product's Buy Now button will
> > be dynamically generated to have the appropriate
code and merchant
> > number for the particular seller of that product.
>
> > So when the customer clicks Buy Now, it will take
them to Google
> > Checkout, and at that point they will complete the
sale with that
> > specific seller. (There is no shopping cart, so
one transaction will
> > only involve one buyer, one product, and one
seller at a time - not
> > multiple products from multiple sellers).
>
> > So far using Google Checkout is no problem, but we
would like to get a
> > notification back from Google Checkout to our
site, when the sale is
> > finished. We are having some problems
understanding which parts of the
> > Google API to use.
>
> > 1) If we use level_2 integration then various
notification options are
> > possible, but each seller would have to give us
their sensitive
> > information like bank account # etc., which we
want to avoid. We want
> > them to only give us their merchant number so that
we can create their
> > Buy Now butotn.
>
> You could use level 2 Notification without intruding on
the Merchant.
>
> You would need their Merchant ID and Merchant Key to
build the button
> correctly, using encrypted xml. You could include a
reference to your
> Merchant in the merchant-private-data which can go into
the enrcrypted string
>
> The merchant would have to place the URL to your
callback script in the
> Merchant Center under Settings->Integration to make
the Notification API
> work.
>
> When a sale is initiated, the callback script would
receive
> the 'new-order-notification' xml stream which contains
the item(s) being
> sold, tax, shipping and address details, the buyer's
Google ID and the
> merchant-private-data which could contain the
Merchant's ID or a reference to
> a record containing the info you need to identify the
Merchant.
>
> The callback script could be the same one for all your
Merchants. No one else
> would be able to use it because only known Merchant
ID/Key combinations can
> access it.
>
> Because you know from the outset which Merchant's goods
are being sold from
> within the callback script, you could provide bespoke
responses tailored to
> the Merchant's needs, as defined somewhere eg in a
database.
>
> Google's callback system is the most complex I've run
across but also the most
> secure.
>
>
>
> > 2) If we use the approach mentioned under
"third party tracking", then
> > we need to apply to be listed under Google's list
of trusted third
> > party vendors, and we are an early-stage startup,
so that seems
> > problematic.
>
> > Are there any other options?
>
> > Thanks for your help/advice,
>
> > Andrew
>
> --
> --------------------------------------------------
> Bob Hutchinson
> Arwystli Networks
>   Linux specialists
>   Server administration
>   Programming
>   Web Hosting
>   Mail Hosting
> web:http://midwales.com
> email: h...arwystli.net
> skype: bobhutch
> ---------------------------------------------------
Hide quoted text -
>
> - Show quoted text -


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "API Integration Basics" group.
To post to this group, send email to
google-checkout-api-integrationgooglegroups.com
To unsubscribe from this group, send email to
google-checkout-api-integration-unsubscribegooglegroups.com
For more options, visit this group at http://groups.google.com/group/google-checko
ut-api-integration?hl=en
-~----------~----~----~----~------~----~------~--~---

On Tuesday 12 June 2007 8:04 pm, BunsenHoneydew wrote:
> This is very helpful. Thank you!
> Andrew

I made (at least) one mistake though, you will have to get
the Merchant ID/Key 
from the Authentication procedure which can be done using
apache/php, don't 
know about other languages.

>
> On Jun 11, 2:12 pm, Bob Hutchinson <h...arwystli.net> wrote:
> > On Monday 11 June 2007 5:12 pm, BunsenHoneydew
wrote:
> > > Hello,
> > >
> > > We are developing a new web site which will
basically be an "indirect
> > > sales channel" for multiple sellers. Our
web site will contain product
> > > information from multiple sellers. Customers
will be able to click a
> > > "Buy Now" button for any product.
Each product's Buy Now button will
> > > be dynamically generated to have the
appropriate code and merchant
> > > number for the particular seller of that
product.
> > >
> > > So when the customer clicks Buy Now, it will
take them to Google
> > > Checkout, and at that point they will
complete the sale with that
> > > specific seller. (There is no shopping cart,
so one transaction will
> > > only involve one buyer, one product, and one
seller at a time - not
> > > multiple products from multiple sellers).
> > >
> > > So far using Google Checkout is no problem,
but we would like to get a
> > > notification back from Google Checkout to our
site, when the sale is
> > > finished. We are having some problems
understanding which parts of the
> > > Google API to use.
> > >
> > > 1) If we use level_2 integration then various
notification options are
> > > possible, but each seller would have to give
us their sensitive
> > > information like bank account # etc., which
we want to avoid. We want
> > > them to only give us their merchant number so
that we can create their
> > > Buy Now butotn.
> >
> > You could use level 2 Notification without
intruding on the Merchant.
> >
> > You would need their Merchant ID and Merchant Key
to build the button
> > correctly, using encrypted xml. You could include
a reference to your
> > Merchant in the merchant-private-data which can go
into the enrcrypted
> > string
> >
> > The merchant would have to place the URL to your
callback script in the
> > Merchant Center under Settings->Integration to
make the Notification API
> > work.
> >
> > When a sale is initiated, the callback script
would receive
> > the 'new-order-notification' xml stream which
contains the item(s) being
> > sold, tax, shipping and address details, the
buyer's Google ID and the
> > merchant-private-data which could contain the
Merchant's ID or a
> > reference to a record containing the info you need
to identify the
> > Merchant.
> >
> > The callback script could be the same one for all
your Merchants. No one
> > else would be able to use it because only known
Merchant ID/Key
> > combinations can access it.
> >
> > Because you know from the outset which Merchant's
goods are being sold
> > from within the callback script, you could provide
bespoke responses
> > tailored to the Merchant's needs, as defined
somewhere eg in a database.
> >
> > Google's callback system is the most complex I've
run across but also the
> > most secure.
> >
> > > 2) If we use the approach mentioned under
"third party tracking", then
> > > we need to apply to be listed under Google's
list of trusted third
> > > party vendors, and we are an early-stage
startup, so that seems
> > > problematic.
> > >
> > > Are there any other options?
> > >
> > > Thanks for your help/advice,
> > >
> > > Andrew
> >
> > --
> >
--------------------------------------------------
> > Bob Hutchinson
> > Arwystli Networks
> >   Linux specialists
> >   Server administration
> >   Programming
> >   Web Hosting
> >   Mail Hosting
> > web:http://midwales.com
> > email: h...arwystli.net
> > skype: bobhutch
> >
--------------------------------------------------- Hide
quoted text -
> >
> > - Show quoted text -
>
> 
-- 
--------------------------------------------------
Bob Hutchinson
Arwystli Networks
  Linux specialists
  Server administration
  Programming
  Web Hosting
  Mail Hosting
web: http://midwales.com
email: hutcharwystli.net
skype: bobhutch
--------------------------------------------------

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "API Integration Basics" group.
To post to this group, send email to
google-checkout-api-integrationgooglegroups.com
To unsubscribe from this group, send email to
google-checkout-api-integration-unsubscribegooglegroups.com
For more options, visit this group at http://groups.google.com/group/google-checko
ut-api-integration?hl=en
-~----------~----~----~----~------~----~------~--~---