Capturing Non-Billing Related Data During Checkout Process ??

bjrupert — Wed, 06 Jul 2011 00:04:29 GMT

Hello,

We are working on a checkout process that we are going to use with Direct Post or SIM API (not sure would like a recommendation based on the app I describe).

We're working on a charity golf tournament and want to sell sponsorships and individual single/foursome rounds. Sponsorships are 'packages' that require the sponsoring organization name, primary point of contact (name, phone, e-mail, address) as well as an included 'Foursome' for the golf tourney.

EXAMPLE: The data that we need to collect for the "Foursome", for example is more than just the purchaser info (name, billing address, CC#, ZIP, etc..) - we'd like to also gather the names and contact info for the four golfers who will be registered for the "Foursome" - there are about 10 more similar product instances that require additional data to be collected other than that of the purchaser/billing info.

QUESTION: Does Authorize.net provide as a feature of the API a method to collect this 'non-billing' related data and pass that info back along to the merchant (the foundation/charity in this case) after the transaction is completed?

If so, what API would allow us to accomplish this in the most straight-forward and simplistic way?

Thanks any info is greatly appreciated - we are in a rush to get this rolled out. We are currently using the 'simple checkout' method and the customer wants something a bit more integrated. Click here for the live site and the products/services being offered.

Thanks,

-BJr

Re: Capturing Non-Billing Related Data During Checkout Process ??

Trevor — Fri, 08 Jul 2011 22:15:37 GMT

I am going to assume that you are planning on continueing to use the payment form hosted by Authorize.Net. If you are generating your own payment form, obviously you can collect whatever information you want. The API that is relavent to using our hosted payment form is the Server Integration Method (SIM).

Our hosted payment form cannot be modified to collect custom fields, however, it is possible to collect that information from the customer on your own site and relay it through our payment form so that it is returned in the transaction response. This capability is what we refer to as Merchant Defined Fields. The SIM API actually allows you to submit any field that you would like, if that field is not otherwise defined in our API, then it will be ignored and simply echoed back to you with the transaction result. You can find the relevent documentation here.

topic Capturing Non-Billing Related Data During Checkout Process ?? in Integration and Testing

Capturing Non-Billing Related Data During Checkout Process ??

Re: Capturing Non-Billing Related Data During Checkout Process ??