X-Git-Url: http://git.freeside.biz/gitweb/?p=Business-OnlinePayment.git;a=blobdiff_plain;f=notes_for_module_writers_v3;h=7313e1108e481aa6fd2767885c319d217ff0ee0a;hp=94b598f75013a52934dc34f1dc3124e9fe475f26;hb=6af0eaebc5acba3715b2575b69c85f3ad5c93a77;hpb=990795fc414232fb5ab67aa5dbc837e5b656b140 diff --git a/notes_for_module_writers_v3 b/notes_for_module_writers_v3 index 94b598f..7313e11 100644 --- a/notes_for_module_writers_v3 +++ b/notes_for_module_writers_v3 @@ -2,14 +2,17 @@ These are the module writer's notes for v3. See the regular "notes_for_module_writers" file first. -- If your gateway is HTTPS-based, use (or convert to) += Business::OnlinePayment::HTTPS = + + If your gateway is HTTPS-based, use (or convert to) Business::OnlinePayment::HTTPS !! + Note: The correct thing for modern B:OP: gateway modules that need to speak HTTPS to do is to use Business::OnlinePayment::HTTPS and depend on "Net::HTTPS::Any" (since B:OP itself doesn't). -- Handling failures: += Handling failures = - If your processor module encounters a setup problem, communication error or other problem that's prevents the card from even being @@ -32,7 +35,7 @@ These are the module writer's notes for v3. See the regular - "decline" (other card/transaction declines only, not other errors) -- (NEW IN 3.01) Introspection: += (NEW IN 3.01) Introspection = - Add an _info subroutine to your module that returns a hashref of information: @@ -92,7 +95,7 @@ These are the module writer's notes for v3. See the regular } -- authorization and order_number (NEWLY DOCUMENTED IN 3.01): += authorization and order_number (NEWLY DOCUMENTED IN 3.01) = Gateways will return one or two values from Authorization Only and Normal Authorization transactions that must be submitted back with a @@ -106,8 +109,34 @@ These are the module writer's notes for v3. See the regular is a unique tranaction id generated by the gateway. -- Moo (NEWLY DOCUMENTED IN 3.04) += Moo (NEWLY DOCUMENTED IN 3.04) = Feel free to write gateway modules which use Moo. Please do not require Moo newer than 0.091011 at this time (until 2018 or so). + += Partial authorizations (NEWLY DOCUMENTED IN 3.04) = + + If your gateway supports partial authorizations: + + - Declare this in your "sub _info" introspection subroutine: + 'partial_auth' => 1, + + - Add "partial_auth_amount to your build_subs call in set_defaults, or add + one: + $self->build_subs('partial_auth_amount'); + + - Honor the transaction 'partial_auth' flag as follows: + + If this transaction flag is unset, the application is not expecting to + handle a partial authorzation. So, either set the gateway flag disabling + partial authorizations, or (if your gatweay does not have such a + setting), immediately void any partial authorization received and + return is_success 0. + + If this transaction flag is set, the application can handle a partial + authorization. Make sure the flag to enable them is passed to the + gateway, if necessary. When a partial authorization is received, the + amount must be returned as "partial_auth_amount": + $self->partial_auth_amount( $partial_amount ); + For normal full authorizations, "partial_auth_amount" must not be set. + +