capturing authorize.net transactions for settlement; workflow for donatables

View: New views
6 Messages — Rating Filter:   Alert me  

capturing authorize.net transactions for settlement; workflow for donatables

by Kyle Cronan :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Hi,

I've gotten to the point where I have a donation form that works with
getpaid.authorizedotnet.  However, I'm only seeing "authorization
only" transactions in my log at authorize.net.  There are no
corresponding "prior authorization capture" transactions.  This is
after I went to the admin-manage-order page and took it through the
"processing" and "delivered" states.  It doesn't look to me like this
transaction is going to settle when my batch runs.

Also, I'd like to not have to manually go in and click a button a
couple times to get the transaction to "delivered."  The capture
should happen right away for a donatable (I can't imagine a situation
where its authorized but we would want to void it).  Even better, the
transaction could be entered as "authorization w/ auto-capture"
instead of "authorization only."  Although that would maybe require a
new method in zc.authorizedotnet.

Am I not getting a capture transaction because I'm currently working
with donatables?  I'm considering changing the transaction type in my
local copy of zc.authorizedotnet to use auto-capture, as a quick fix.
But I don't want to break shippables, which I'm planning on using
later on.  Any thoughts?

Thanks,
Kyle

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "getpaid-dev" group.
To post to this group, send email to getpaid-dev@...
To unsubscribe from this group, send email to getpaid-dev+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/getpaid-dev?hl=en
-~----------~----~----~----~------~----~------~--~---


Re: capturing authorize.net transactions for settlement; workflow for donatables

by Rob LaRubbio-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Are you using the production authorize.net, or their test processor?  For the production server you need to move it out of testing mode and into production mode before it will accept settle requests.  GetPaid should always issue an authorize and then a settle request at the end of the checkout pipeline regardless of if you have a shippable or donatable (although shippable probably should wait until it is marked as delivered)

-Rob

On Thu, Jul 30, 2009 at 8:45 PM, Kyle Cronan <kyle@...> wrote:

Hi,

I've gotten to the point where I have a donation form that works with
getpaid.authorizedotnet.  However, I'm only seeing "authorization
only" transactions in my log at authorize.net.  There are no
corresponding "prior authorization capture" transactions.  This is
after I went to the admin-manage-order page and took it through the
"processing" and "delivered" states.  It doesn't look to me like this
transaction is going to settle when my batch runs.

Also, I'd like to not have to manually go in and click a button a
couple times to get the transaction to "delivered."  The capture
should happen right away for a donatable (I can't imagine a situation
where its authorized but we would want to void it).  Even better, the
transaction could be entered as "authorization w/ auto-capture"
instead of "authorization only."  Although that would maybe require a
new method in zc.authorizedotnet.

Am I not getting a capture transaction because I'm currently working
with donatables?  I'm considering changing the transaction type in my
local copy of zc.authorizedotnet to use auto-capture, as a quick fix.
But I don't want to break shippables, which I'm planning on using
later on.  Any thoughts?

Thanks,
Kyle




--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "getpaid-dev" group.
To post to this group, send email to getpaid-dev@...
To unsubscribe from this group, send email to getpaid-dev+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/getpaid-dev?hl=en
-~----------~----~----~----~------~----~------~--~---


Re: capturing authorize.net transactions for settlement; workflow for donatables

by Kyle Cronan :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


I'm using the production server with real transactions, not test mode. -Kyle

On Fri, Jul 31, 2009 at 10:04 AM, Rob LaRubbio<larubbio@...> wrote:

> Are you using the production authorize.net, or their test processor?  For
> the production server you need to move it out of testing mode and into
> production mode before it will accept settle requests.  GetPaid should
> always issue an authorize and then a settle request at the end of the
> checkout pipeline regardless of if you have a shippable or donatable
> (although shippable probably should wait until it is marked as delivered)
>
> -Rob
>
> On Thu, Jul 30, 2009 at 8:45 PM, Kyle Cronan <kyle@...> wrote:
>>
>> Hi,
>>
>> I've gotten to the point where I have a donation form that works with
>> getpaid.authorizedotnet.  However, I'm only seeing "authorization
>> only" transactions in my log at authorize.net.  There are no
>> corresponding "prior authorization capture" transactions.  This is
>> after I went to the admin-manage-order page and took it through the
>> "processing" and "delivered" states.  It doesn't look to me like this
>> transaction is going to settle when my batch runs.
>>
>> Also, I'd like to not have to manually go in and click a button a
>> couple times to get the transaction to "delivered."  The capture
>> should happen right away for a donatable (I can't imagine a situation
>> where its authorized but we would want to void it).  Even better, the
>> transaction could be entered as "authorization w/ auto-capture"
>> instead of "authorization only."  Although that would maybe require a
>> new method in zc.authorizedotnet.
>>
>> Am I not getting a capture transaction because I'm currently working
>> with donatables?  I'm considering changing the transaction type in my
>> local copy of zc.authorizedotnet to use auto-capture, as a quick fix.
>> But I don't want to break shippables, which I'm planning on using
>> later on.  Any thoughts?
>>
>> Thanks,
>> Kyle
>>
>>
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "getpaid-dev" group.
To post to this group, send email to getpaid-dev@...
To unsubscribe from this group, send email to getpaid-dev+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/getpaid-dev?hl=en
-~----------~----~----~----~------~----~------~--~---


Re: capturing authorize.net transactions for settlement; workflow for donatables

by Rob LaRubbio-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Is there any error you can send along?  Or maybe the list of transitions from the order management console?

On Fri, Jul 31, 2009 at 8:18 AM, Kyle Cronan <kyle@...> wrote:

I'm using the production server with real transactions, not test mode. -Kyle

On Fri, Jul 31, 2009 at 10:04 AM, Rob LaRubbio<larubbio@...> wrote:
> Are you using the production authorize.net, or their test processor?  For
> the production server you need to move it out of testing mode and into
> production mode before it will accept settle requests.  GetPaid should
> always issue an authorize and then a settle request at the end of the
> checkout pipeline regardless of if you have a shippable or donatable
> (although shippable probably should wait until it is marked as delivered)
>
> -Rob
>
> On Thu, Jul 30, 2009 at 8:45 PM, Kyle Cronan <kyle@...> wrote:
>>
>> Hi,
>>
>> I've gotten to the point where I have a donation form that works with
>> getpaid.authorizedotnet.  However, I'm only seeing "authorization
>> only" transactions in my log at authorize.net.  There are no
>> corresponding "prior authorization capture" transactions.  This is
>> after I went to the admin-manage-order page and took it through the
>> "processing" and "delivered" states.  It doesn't look to me like this
>> transaction is going to settle when my batch runs.
>>
>> Also, I'd like to not have to manually go in and click a button a
>> couple times to get the transaction to "delivered."  The capture
>> should happen right away for a donatable (I can't imagine a situation
>> where its authorized but we would want to void it).  Even better, the
>> transaction could be entered as "authorization w/ auto-capture"
>> instead of "authorization only."  Although that would maybe require a
>> new method in zc.authorizedotnet.
>>
>> Am I not getting a capture transaction because I'm currently working
>> with donatables?  I'm considering changing the transaction type in my
>> local copy of zc.authorizedotnet to use auto-capture, as a quick fix.
>> But I don't want to break shippables, which I'm planning on using
>> later on.  Any thoughts?
>>
>> Thanks,
>> Kyle
>>
>>
>
>
> >
>




--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "getpaid-dev" group.
To post to this group, send email to getpaid-dev@...
To unsubscribe from this group, send email to getpaid-dev+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/getpaid-dev?hl=en
-~----------~----~----~----~------~----~------~--~---


Re: capturing authorize.net transactions for settlement; workflow for donatables

by Kyle Cronan :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


I do have this in my error log:

2009-07-30T21:31:31 WARNING PloneFormGen Designated action adapter
'mailer' is missing; ignored.
------
2009-07-30T21:31:31 WARNING PloneFormGen Designated action adapter
'getpaidpfgadapter.2009-07-30.8724498219' is missing; ignored.

Order Log:
kyle 2009-07-30 22:42:24.034123 - Create NEW
kyle 2009-07-30 22:42:24.036793 - Create REVIEWING
kyle 2009-07-30 22:42:24.997744 REVIEWING Authorize CHARGEABLE
kyle 2009-07-30 22:42:24.998481 CHARGEABLE Charge Order CHARGING
kyle 2009-07-30 22:42:25.545079 CHARGING Processor Charged CHARGED
kyle 2009-07-30 22:48:11.035787 NEW Process Order PROCESSING
kyle 2009-07-30 22:52:38.400583 PROCESSING Order Processed DELIVERED

Thanks,
Kyle


On Fri, Jul 31, 2009 at 11:05 AM, Rob LaRubbio<larubbio@...> wrote:

> Is there any error you can send along?  Or maybe the list of transitions
> from the order management console?
>
> On Fri, Jul 31, 2009 at 8:18 AM, Kyle Cronan <kyle@...> wrote:
>>
>> I'm using the production server with real transactions, not test mode.
>> -Kyle
>>
>> On Fri, Jul 31, 2009 at 10:04 AM, Rob LaRubbio<larubbio@...> wrote:
>> > Are you using the production authorize.net, or their test processor?
>> > For
>> > the production server you need to move it out of testing mode and into
>> > production mode before it will accept settle requests.  GetPaid should
>> > always issue an authorize and then a settle request at the end of the
>> > checkout pipeline regardless of if you have a shippable or donatable
>> > (although shippable probably should wait until it is marked as
>> > delivered)
>> >
>> > -Rob
>> >
>> > On Thu, Jul 30, 2009 at 8:45 PM, Kyle Cronan <kyle@...> wrote:
>> >>
>> >> Hi,
>> >>
>> >> I've gotten to the point where I have a donation form that works with
>> >> getpaid.authorizedotnet.  However, I'm only seeing "authorization
>> >> only" transactions in my log at authorize.net.  There are no
>> >> corresponding "prior authorization capture" transactions.  This is
>> >> after I went to the admin-manage-order page and took it through the
>> >> "processing" and "delivered" states.  It doesn't look to me like this
>> >> transaction is going to settle when my batch runs.
>> >>
>> >> Also, I'd like to not have to manually go in and click a button a
>> >> couple times to get the transaction to "delivered."  The capture
>> >> should happen right away for a donatable (I can't imagine a situation
>> >> where its authorized but we would want to void it).  Even better, the
>> >> transaction could be entered as "authorization w/ auto-capture"
>> >> instead of "authorization only."  Although that would maybe require a
>> >> new method in zc.authorizedotnet.
>> >>
>> >> Am I not getting a capture transaction because I'm currently working
>> >> with donatables?  I'm considering changing the transaction type in my
>> >> local copy of zc.authorizedotnet to use auto-capture, as a quick fix.
>> >> But I don't want to break shippables, which I'm planning on using
>> >> later on.  Any thoughts?
>> >>
>> >> Thanks,
>> >> Kyle
>> >>
>> >>
>> >
>> >
>> > >
>> >
>>
>>
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "getpaid-dev" group.
To post to this group, send email to getpaid-dev@...
To unsubscribe from this group, send email to getpaid-dev+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/getpaid-dev?hl=en
-~----------~----~----~----~------~----~------~--~---


Re: capturing authorize.net transactions for settlement; workflow for donatables

by Kyle Cronan :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Oh, sorry, never mind.  It did end up settling when my batch ran, I
just couldn't see the capture transaction through the authorize.net
website.  It was only showing me "authorization only."

I'm set to go for donations.  I'm just going to need to figure out
that other error message when I get to the point where I need to use a
shopping cart setup.

Thanks,
Kyle


On Fri, Jul 31, 2009 at 12:06 PM, Kyle Cronan<kyle@...> wrote:

> I do have this in my error log:
>
> 2009-07-30T21:31:31 WARNING PloneFormGen Designated action adapter
> 'mailer' is missing; ignored.
> ------
> 2009-07-30T21:31:31 WARNING PloneFormGen Designated action adapter
> 'getpaidpfgadapter.2009-07-30.8724498219' is missing; ignored.
>
> Order Log:
> kyle    2009-07-30 22:42:24.034123      -                       Create                  NEW
> kyle    2009-07-30 22:42:24.036793      -                       Create                  REVIEWING
> kyle    2009-07-30 22:42:24.997744      REVIEWING       Authorize                       CHARGEABLE
> kyle    2009-07-30 22:42:24.998481      CHARGEABLE      Charge Order            CHARGING
> kyle    2009-07-30 22:42:25.545079      CHARGING        Processor Charged       CHARGED
> kyle    2009-07-30 22:48:11.035787      NEW             Process Order           PROCESSING
> kyle    2009-07-30 22:52:38.400583      PROCESSING      Order Processed         DELIVERED
>
> Thanks,
> Kyle
>
>
> On Fri, Jul 31, 2009 at 11:05 AM, Rob LaRubbio<larubbio@...> wrote:
>> Is there any error you can send along?  Or maybe the list of transitions
>> from the order management console?
>>
>> On Fri, Jul 31, 2009 at 8:18 AM, Kyle Cronan <kyle@...> wrote:
>>>
>>> I'm using the production server with real transactions, not test mode.
>>> -Kyle
>>>
>>> On Fri, Jul 31, 2009 at 10:04 AM, Rob LaRubbio<larubbio@...> wrote:
>>> > Are you using the production authorize.net, or their test processor?
>>> > For
>>> > the production server you need to move it out of testing mode and into
>>> > production mode before it will accept settle requests.  GetPaid should
>>> > always issue an authorize and then a settle request at the end of the
>>> > checkout pipeline regardless of if you have a shippable or donatable
>>> > (although shippable probably should wait until it is marked as
>>> > delivered)
>>> >
>>> > -Rob
>>> >
>>> > On Thu, Jul 30, 2009 at 8:45 PM, Kyle Cronan <kyle@...> wrote:
>>> >>
>>> >> Hi,
>>> >>
>>> >> I've gotten to the point where I have a donation form that works with
>>> >> getpaid.authorizedotnet.  However, I'm only seeing "authorization
>>> >> only" transactions in my log at authorize.net.  There are no
>>> >> corresponding "prior authorization capture" transactions.  This is
>>> >> after I went to the admin-manage-order page and took it through the
>>> >> "processing" and "delivered" states.  It doesn't look to me like this
>>> >> transaction is going to settle when my batch runs.
>>> >>
>>> >> Also, I'd like to not have to manually go in and click a button a
>>> >> couple times to get the transaction to "delivered."  The capture
>>> >> should happen right away for a donatable (I can't imagine a situation
>>> >> where its authorized but we would want to void it).  Even better, the
>>> >> transaction could be entered as "authorization w/ auto-capture"
>>> >> instead of "authorization only."  Although that would maybe require a
>>> >> new method in zc.authorizedotnet.
>>> >>
>>> >> Am I not getting a capture transaction because I'm currently working
>>> >> with donatables?  I'm considering changing the transaction type in my
>>> >> local copy of zc.authorizedotnet to use auto-capture, as a quick fix.
>>> >> But I don't want to break shippables, which I'm planning on using
>>> >> later on.  Any thoughts?
>>> >>
>>> >> Thanks,
>>> >> Kyle
>>> >>
>>> >>
>>> >
>>> >
>>> > >
>>> >
>>>
>>>
>>
>>
>> >>
>>
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "getpaid-dev" group.
To post to this group, send email to getpaid-dev@...
To unsubscribe from this group, send email to getpaid-dev+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/getpaid-dev?hl=en
-~----------~----~----~----~------~----~------~--~---