Is there valid credit card info we can pass the Payment API to get a successful response?

  • Question
  • Updated 6 years ago
  • Answered
Is there valid credit card info we can pass the Payment API to get a successful response? Since I'm doing local dev, without SSL, I'd rather not pass my personal credit card info through.

But right now any test numbers [https://www.paypal.com/en_US/vhelp/pa...] I try are returning a 403 (Forbidden) error.
Photo of Josh Pigford

Josh Pigford

  • 14 Posts
  • 0 Reply Likes

Posted 6 years ago

  • 2
Photo of Nathaniel Talbott

Nathaniel Talbott, Official Rep

  • 969 Posts
  • 94 Reply Likes
Yes, on a test site you can use these cards:

4222222222222 - Good Visa
4012888888881881 - Unauthorized Visa
4111111111111111 - Gateway Unavailable Visa

It's on my list to add these to the documentation, just haven't gotten around to it yet.
Photo of Josh Pigford

Josh Pigford

  • 14 Posts
  • 0 Reply Likes
I'm using the Good Visa and it's still returning 403 with "The payment system is not responding."

I've tried this on both a test and production Spreedly site.
Photo of Nathaniel Talbott

Nathaniel Talbott, Official Rep

  • 969 Posts
  • 94 Reply Likes
Not sure why you're getting that error - it seems to only be affecting you. We'll investigate first thing in the morning - sorry for the trouble
Photo of Nathaniel Talbott

Nathaniel Talbott, Official Rep

  • 969 Posts
  • 94 Reply Likes
OK, this was a case of bad documentation - totally our fault. The problem is not specifying the card_type field, which wasn't in the documentation till today. I just updated the docs, including the test card numbers and the valid card_types:

http://spreedly.com/manual/integratio...

Give it a whirl and let me know if it's working for you now - sorry for the trouble!
Photo of Nash Kabbara

Nash Kabbara

  • 20 Posts
  • 1 Reply Like
Still same issue for me:

curl -u ...:X \
-X PUT -H 'Content-Type: application/xml' \
-d '\

4111111111111111
visa
234
1
2011
Joe
Bob

' \
https://spreedly.com/api/v4/tzza/invo...

The error is very misleading. Even if that were the problem.
Photo of Nathaniel Talbott

Nathaniel Talbott, Official Rep

  • 969 Posts
  • 94 Reply Likes
You're using the card number that generates a "gateway not available" error, so it's actually doing the right thing. Switch to "4222222222222" and it should go through successfully.

Let me know how it goes...
Photo of Nash Kabbara

Nash Kabbara

  • 20 Posts
  • 1 Reply Like
Cool, it went through, but still got "The payment system is not responding" instead of "gateway not available.". Are these the same?
Photo of Nash Kabbara

Nash Kabbara

  • 20 Posts
  • 1 Reply Like
Meaning with the 411111... number.
Photo of Nathaniel Talbott

Nathaniel Talbott, Official Rep

  • 969 Posts
  • 94 Reply Likes
Yup. And FYI, we do need to improve the error messages some more - that's definitely on our list.
Photo of Nash Kabbara

Nash Kabbara

  • 20 Posts
  • 1 Reply Like
OK, great.

Has the payment API been tested in production for some period of time?

I'm a little nervous finding this bug.
Photo of Nash Kabbara

Nash Kabbara

  • 20 Posts
  • 1 Reply Like
sorry, not bug, missing documentation. I keep hitting enter too fast. Sorry.
Photo of Nathaniel Talbott

Nathaniel Talbott, Official Rep

  • 969 Posts
  • 94 Reply Likes
It's definitely newer than our hosted interface, but 90% of the code is shared between the hosted interface and the API, so we're quite confident in the underlying functionality. Definitely still hitting a few documentation glitches as people ramp up on it, though - sorry about that.