Error processing credit card

89 views
Skip to first unread message

Axel Perkins

unread,
Dec 2, 2013, 8:35:06 AM12/2/13
to activem...@googlegroups.com

Hello everyone,

while processing a credit card payment using Spree Commerce / Active Merchant and choosing Paymill as gateway, we got a "Server Error" with the attached log (card number modified).
Paymill (the gateway company) says the transaction was successful and the money was transfered. Now we are a bit clueless how to interpret the log. Can anyone interpret this? Why, conceptually is it even possible to get an 
ActiveMerchant::Billing::MultiResponse containing an array of multiple, and in this case, contradicting responses?

Processing by Spree::CheckoutController#update as HTML

   Parameters: {"utf8"=>"✓", "authenticity_token"=>"5caL3iBfD/MGQrAy2Q9DR66FUBpxFVMay87Lr+0xz+w=", "order"=>{"payments_attributes"=>[{"payment_method_id"=>"7"}], "coupon_code"=>""}, "payment_source"=>{"7"=>{"number"=>"[FILTERED]", "expiry"=>"04 / 17", "verification_value"=>"[FILTERED]", "cc_type"=>"visa", "first_name"=>"azin", "last_name"=>"azadi"}}, "state"=>"payment"}

 Gateway Error

   --- !ruby/object:ActiveMerchant::Billing::MultiResponse

 responses:

 - !ruby/object:ActiveMerchant::Billing::Response

       account:

   params:

     transaction:

         binCountry: DE

         brand: VISA

         bin: '455578'

         expiry:

           month: '01'

           year: '2020'

         last4Digits: "0815\r\n"

       channel: 8a8394c442584b0801426b2035bf1709

         code: CC.RG

         holder: ''

         address:

       customer:

         shortId: 7141.4413.3394

       identification:

         contact:

         uniqueId: 8a83948b42a44c8b0142b3688f8c32e1

         reason:

           country: DE

           message: Successful+Processing

         result: ACK

           ip: 54.217.46.192

           ipCountry: ie

           code: '00'

       response: SYNC

         return:

           code: 000.000.000

       processing:

       mode: LIVE

       payment:

         code: CC.RG.90.00

           message: Transaction+succeeded

   message: Transaction+succeeded

         timestamp: 2013-12-02+13%3A04%3A03

   test: false

   fraud_review: 

     message: 

     code: 

   success: true

   test: false

     code: 

   message: Server Error

     postal_match: 

   cvv_result:

     code: 

 primary_response: :last

     message: 

     street_match: 

   fraud_review: 

   avs_result:

   authorization: 8a83948b42a44c8b0142b3688f8c32e1

     street_match: 

     postal_match: 

     code: 

     message: 

   params:

 - !ruby/object:ActiveMerchant::Billing::Response

   cvv_result:

   authorization: 

   success: false

     error: Server Error

     exception: Exception

 

     message: 

 Redirected to https://capetimes-staging.herokuapp.com/checkout/payment

   avs_result:

Nathaniel Talbott

unread,
Dec 2, 2013, 8:55:30 AM12/2/13
to activem...@googlegroups.com
Axel, a fix for this just got merged this past week:


The commit has a lot of details if you're curious as to what was broken.

--
Nathaniel


--
You received this message because you are subscribed to the Google Groups "Active Merchant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to activemerchan...@googlegroups.com.
To post to this group, send email to activem...@googlegroups.com.
Visit this group at http://groups.google.com/group/activemerchant.
For more options, visit https://groups.google.com/groups/opt_out.

Axel Perkins

unread,
Dec 2, 2013, 10:00:59 AM12/2/13
to activem...@googlegroups.com
Wow, that's rather recent :-) thanks!

So do I have to specify a certain SHA1 in my Gemfile to get this fix? 
    bundle update --source activemerchant 
did not change anything...

Nathaniel Talbott

unread,
Dec 2, 2013, 10:02:37 AM12/2/13
to activem...@googlegroups.com
I would imagine so; the fix isn't in a released ActiveMerchant yet. I also don't know how Spree's ActiveMerchant dependency is set up; you may have to tweak things there instead.

--
Nathaniel

Axel Perkins

unread,
Dec 2, 2013, 11:14:51 AM12/2/13
to activem...@googlegroups.com
We got it working perfectly now by using the latest version of activemerchant. 
Thanks so much, Nathaniel!
Axel
Reply all
Reply to author
Forward
0 new messages