active_merchant: VisaNet Peru exception

@shasum you’re probably best positioned to look into this? Not sure under what circumstance the merchant id is not being returned?

#<TypeError: no implicit conversion of nil into String>

/srv/core/current/vendor/bundle/ruby/2.1.0/bundler/gems/active_merchant-fc32c3ca8d6a/lib/active_merchant/billing/gateways/visanet_peru.rb:155:in `+'
/srv/core/current/vendor/bundle/ruby/2.1.0/bundler/gems/active_merchant-fc32c3ca8d6a/lib/active_merchant/billing/gateways/visanet_peru.rb:155:in `url'
/srv/core/current/vendor/bundle/ruby/2.1.0/bundler/gems/active_merchant-fc32c3ca8d6a/lib/active_merchant/billing/gateways/visanet_peru.rb:127:in `commit'
/srv/core/current/vendor/bundle/ruby/2.1.0/bundler/gems/active_merchant-fc32c3ca8d6a/lib/active_merchant/billing/gateways/visanet_peru.rb:38:in `authorize'
/srv/core/current/vendor/bundle/ruby/2.1.0/bundler/gems/active_merchant-fc32c3ca8d6a/lib/active_merchant/billing/gateways/visanet_peru.rb:22:in `block (2 levels) in purchase'
/srv/core/current/vendor/bundle/ruby/2.1.0/bundler/gems/active_merchant-fc32c3ca8d6a/lib/active_merchant/billing/response.rb:59:in `process'

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 23 (23 by maintainers)

Commits related to this issue

Most upvoted comments

@rwdaigle the issue we’ve seen is that ActiveMerchant users that operate across many different gateways use a common order_id that’s relevant to their system, which doesn’t necessarily conform to the requirements for a given gateway. If we don’t clean it up for them, they have to know the requirements for each gateway they’re dealing with.