Authentication Options

In addition, these IP addresses/Connection Usernames must be affiliated
with the Merchant IDs for which the client should be submitting
transactions.

This does allow Third Party Hosting service organizations presenting on
behalf of other merchants to submit transactions. However, each time a new
customer is added, the merchant or Third-Party hosting organization needs
to ensure that the new Merchant IDs or Chain IDs are affiliated with the
hosting companies IPs or Connection Usernames.

If the merchant expects to have more than one merchant account with the
Orbital Gateway, it should have its IP addresses/Connection Usernames
affiliated at the Chain level hierarchy within the Orbital Gateway. Each
time a new merchant ID is added, as long as it is placed within the same
Chain, it will simply work. Otherwise, the additional MIDs will need to be
affiliated with the merchant IPs or Connection Usernames respectively. For
example, we generally affiliate all Salem accounts [BIN 000001] with their
Company Number [formerly called MA #] number so all MIDs or Divisions under
that Company will automatically be affiliated.

#void(authorization, options = {}, deprecated = {}) ⇒ Object

238
239
240
241
242
243
244
245
246

# File 'lib/active_merchant/billing/gateways/orbital.rb', line 238defvoid(authorization,options={},deprecated={})if(!options.kind_of?(Hash))ActiveMerchant.deprecated("Calling the void method with an amount parameter is deprecated and will be removed in a future version.")returnvoid(options,deprecated.merge(:amount=>authorization))endorder=build_void_request_xml(authorization,options)commit(order,:void,options[:trace_number])end