Closed (fixed)
Project:
Commerce Stripe
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
25 Nov 2014 at 20:14 UTC
Updated:
25 Dec 2017 at 19:59 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
aviindub commentedsounds like a reasonable feature for 2.0
Comment #2
garen24 commentedLooking forward to it. Thanks!
Comment #3
jehu commentedI've created a patch on base of version 7.x-1.x
Comment #4
torgospizzaI think 2.x is shelved (For now anyway) so setting it back and setting to Needs review.
Comment #5
kingdutchMoving to 3.x as it seems more alive than 1.x
It also seems that in the Stripe API the error.code has been replaced by error.type. Furthermore the error I encounter is:
In the attached patch the above error type with message has been added to what Jehu did in #3. What will need to be checked is whether the other types are still correct in the latest API version.
Comment #6
kingdutchIt turns out that the response from Stripe contains a type and sometimes a code if there are multiple different messages within the same type. Two examples below.
So we first check if there's a specific code and fall back to the type otherwise.
Comment #7
shi99 commentedPatch in #6 worked for me.
Thanks.
Comment #8
alex.bukach commentedPatch in #6 worked for me as well. Thanks!
Comment #9
torgospizzaThanks, everyone! Committed to dev.