Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author Sean Voss

    (@seanvoss)

    Hey skunkbad,

    It’s a payment term.
    https://www.corecommerce.com/kb/17221/authorize_vs_authorize_and_capture

    Basically you are authorizing the card, and then capture the transaction once the goods have shipped.

    Thread Starter skunkbad

    (@skunkbad)

    Hi Sean. When I did my test transaction, with “Authorization & Capture” checked, it seemed like I still needed to go in and complete the order. I do want the card to be authorized and captured(charged) immediately, and without any interaction on my part. So I should leave the checkbox checked, right?

    I guess I’m confused because after the transaction, the order shows that I should “complete” it under actions.

    When I go to my Stripe account, it says “an uncaptured charge was created for …”

    This is with the “Authorization & Capture” checkbox checked.

    Thread Starter skunkbad

    (@skunkbad)

    I’m just wondering if the actual result of the setting is flipped when calling Stripe_Charge::create(). I reviewed the plugin code, and in both instances on line 172 and 181 of stripe_gateway.php, the “capture” array element’s value has a exclamation point in front of it, essentially flipping it’s value. By default, the value is true (boolean) according to the Stripe API, but if the plugin setting for capture is ‘yes’, the value sent to Stripe will be false. Should not the exclamation points be removed?

    Plugin Author Sean Voss

    (@seanvoss)

    So I think it makes sense as is.

    If Enable Authorization and Capture is unchecked the transaction will complete immediately correct?

    The “Capture” in the code and Enable Auth and Capture mean two different things, the different being “Auth”, so by saying you want Auth and Capture it means DON’T capture at time of sale.

    Then when you complete the transaction it becomes captured.

    Thread Starter skunkbad

    (@skunkbad)

    OK, I see how you have described Auth & Capture is different than any other payment gateway I have worked with, so that’s why I was confused. Authorize.net, Linkpoint, and even Stripe consider a captured transaction to be instantly captured, not the logic you have described. Anyways, thanks for writing the plugin. Maybe someday when I’m bored I will write my own. It’s free, so can’t complain, right?

    Plugin Author Sean Voss

    (@seanvoss)

    Hmm yea our nomenclature is not jiving, but it’s a simple boolean so if one works the way you want, that’s all good.

    Paypal I feel like in the article describes it exactly as I wrote it. Auth/Capture means the system will delay capture.
    https://developer.paypal.com/docs/classic/admin/intro/#auth-capture

    Hi Sean,

    Thanks for building this great plugin! I just wanted to offer some feedback about the label on this feature. It was confusing to me as well.

    Perhaps “Enable Authorization & Capture (Manual capture).” would be more clear? Or something like that?

    Is there a way to force the capture to happen automatically? We are using this on a site that sells event tickets, so the cards must be charged at the time of order.

    I am guessing, this may be more of a Woo question, as what needs to happen is that the orders, (for us) need to go straight to complete as opposed to ‘processing’??

    Would that be right?

    I was looking into this very question! I’m definitely not AT ALL familiar with payment gateway-speak, and I misunderstood that Auth & Capture = Auth Now, Capture Manually Later. Thank you for this conversation which gave me my answer right away! I can see now how that label makes sense.

    Great job on the plug-in. It is a HUGE help to my small business trying to get going without having to shell out another $80 just to be able to start selling products (hopefully!).

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘What is "Authorization and Capture" setting?’ is closed to new replies.