- If your gateway is HTTPS-based, use (or convert to)
Business::OnlinePayment::HTTPS !!
-
- - Business::OnlinePayment::OpenECHO is the first "v3-ish" module, try
- starting from there.
+ 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:
'gateway_url' => 'http://www.example.com/',
'module_version' => $VERSION,
'supported_types' => [ qw( CC ECHECK ) ],
+ 'token_support' => 0, #card storage/tokenization support
+ 'test_transaction' => 0, #set true if ->test_transaction(1) works
'supported_actions' => [
'Normal Authorization',
'Authorization Only',
'module_version' => $VERSION,
'module_notes' => 'usage notes',
'supported_types' => [ qw( CC ECHECK ) ],
+ 'token_support' => 1,
+ 'test_transaction' => 1,
'supported_actions' => { 'CC' => [
'Normal Authorization',
'Authorization Only',
],
},
'CC_void_requires_card' => 1,
+ 'ECHECK_void_requires_account' => 1, #routing_code, account_number, name
};
}
+- 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
+ Post Authorization, Void, or Credit transaction.
+
+ If the gateway returns one value, return this as "authorization"
+
+ If the gateway returns two values, return one as "authorization" and the
+ other as "order_number". Typically "authorization" is the more low-level
+ value returned from the underlying processing network while "order_number"
+ is a unique tranaction id generated by the gateway.
+
+
+- Moo (NEWLY DOCUMENTED IN 3.04)
+
+ Feel free to write gateway modules which use Moo. It would be appreciated
+ if you did not use features which required Moo newer than 0.091011 at this
+ time (2014 - 2018).