n&#47 in Authorize.NET transaction when address is not given

[vanboom]

The AuthorizeNetGateway method is assigning n/a or NC as defaults when attempting to extract the state from the address. When the address is nil, n/a causes some junk in the state field of the request. Recommend allowing the state to be nil if it is not provided by the user - why default to NC or n/a. NC is a valid state, but n/a certainly is not a valid state name or abbreviation. We see this come back in the response payload as shown below. Curious if this could cause flags on the processor side w/r to the address verification / fraud settings. I think it should simply allow nil to pass as the value.

NOTE: the other Authorize gateways AuthorizeNetArbGateway and AuthorizeNetCimGateway do not have this default logic and will simply let a nil state pass through when an address is not given.

...
"address" => "",
"city" => "",
"state" => "n/a",
"zip_code" => "75760",
"country" => "",
"phone" => "",
"fax" => "",

active_merchant/lib/active_merchant/billing/gateways/authorize_net.rb

Line 818 in 8575398

address[:state] || 'n/a'

[github-actions]

To provide a cleaner slate for the maintenance of the library, this PR/Issue is being labeled stale after 60 days without activity. It will be closed in 14 days unless you comment with an update regarding its applicability to the current build. Thank you!