Home → Suggestions →

Test Credit Card Number

nash

27 Jan, 2010 02:45 AM via web

Admin Functions

• Edit
• Remove

Using 1 or 2 in order to test approvals and declines is a little inconvenient when testing the app. Mostly because 1 or 2 won't pass the local credit card validation.

Maybe it's better to allow for bogus, but valid CC numbers like 4111111111111111 and use the month field as a trigger for approvals, declines and errors?

Thanks.

-Nash

1. Support Staff 2 Posted by David H. - Chargify on 27 Jan, 2010 04:17 AM

   

   Nash,

   Great point. I have seen Verisign and a few others use that 4111111111111111 and a 4111111111111117 for failure I think. We will take a look at this to make this improvement.

   Admin Functions

   • Edit
   • Remove

2. Support Staff 3 Posted by David H. - Chargify on 02 Feb, 2010 07:25 PM

   

   Nash,

   This is confirmation this issue has been added to Tracker and will get worked on, no ETA at this time.

   Admin Functions

   • Edit
   • Remove

3. David H. - Chargify resolved this discussion on 02 Feb, 2010 07:25 PM.

4. nash re-opened this discussion on 13 Apr, 2010 04:25 PM

5. 4 Posted by nash on 13 Apr, 2010 04:25 PM

   

   Guys,

   Any update on this one by any chance?

   When testing, I have to disable the validations in our app in staging in order to test things. Having a valid CC would greatly help.

   Thanks.

   -Nash

   Admin Functions

   • Edit
   • Split
   • Remove

6. Support Staff 5 Posted by Lance W. - Chargify on 13 Apr, 2010 05:23 PM

   

   Hey Nash,

   I just realized this thread goes back to Feb.

   We're all together this week in Denver, and we'll be reviewing stories and feature requests on Wed and Thu.

   This has not been done, but it has been requested a few times and it seems like it would be relatively easy.

   Thx.

   --- Lance

   Admin Functions

   • Edit
   • Remove

7. Support Staff 6 Posted by Lance W. - Chargify on 18 Apr, 2010 06:59 PM

   

   Hi again, Nash,

   What test cc numbers would pass your front-end systems?

   I saw that DavidH suggested 4111111111111111 and 4111111111111117 back in Feb.

   Thx.

   --- Lance

   Admin Functions

   • Edit
   • Remove

8. 7 Posted by nash on 18 Apr, 2010 07:35 PM

   

   Any valid one would work. It Just has to pass the checksum tests.

   Admin Functions

   • Edit
   • Split
   • Remove

9. Support Staff 8 Posted by Lance W. - Chargify on 18 Apr, 2010 07:38 PM

   

   Okay, thanks. One of the guys will need to see what's "real enough" to use this way, without using something that might actually be someone's credit card :-)

   --- Lance

   Admin Functions

   • Edit
   • Remove

10. Support Staff 9 Posted by Lance W. - Chargify on 25 Apr, 2010 04:28 AM

    

    Hey Nash,

    I just put this test credit card number topic in chargify.uservoice.com , it's a better place to keep track of it and let others vote, too.

    I'm going to close this ticket.

    Thanks.

    --- Lance

    Admin Functions

    • Edit
    • Remove

11. Lance W. - Chargify resolved this discussion on 25 Apr, 2010 04:28 AM.

12. nash re-opened this discussion on 15 May, 2010 10:29 PM

13. 10 Posted by nash on 15 May, 2010 10:29 PM

    

    Lance,

    I couldn't find this in uservoice. It's hard to search their site. Do you have a link?

    Thanks.

    -Nash

    Admin Functions

    • Edit
    • Split
    • Remove

14. Support Staff 11 Posted by Lance W. - Chargify on 18 May, 2010 12:52 AM

    

    Hey,

    Odd, I know it was there, but now I couldn't find it, either, so I just re-created it and gave it one of my votes :-).

    http://chargify.uservoice.com/forums/57052-make-chargify-better-/su...

    --- Lance

    Admin Functions

    • Edit
    • Remove

15. Lance W. - Chargify resolved this discussion on 18 May, 2010 12:52 AM.

Comments are currently closed for this discussion. You can start a new one.