How do we test a payment declined and other error conditions?

  1. #1 Posted by Dean on 28 Aug, 2013 07:41 PM

    Hi Duane! You can test a declined payment by setting the customer's billing zip code to 96000. When the simulated transaction is executed, the gateway response will be a declined transaction.

    There are several other testing codes here in the docs: http://support.cheddargetter.com/kb/api-8/error-handling#error-codes. Simply add a 9 in front of the Aux code (e.g. 9XXXX) associated with the event you'd like to test and set that as the customer's zip.

    Let me know if you still have questions!

    Best,
    Dean

  2. #2 Posted by Duane Roumel on 28 Aug, 2013 07:44 PM

    On Wed, Aug 28, 2013 at 3:41 PM, Dean <
    [email blocked]> wrote:

    > You can test a declined payment by setting the customer's billing zip code
    > to 96000

    Great, Thanks for that info. We also need to know how we can test a past
    due status without having to wait for the bill date to pass.

    --
    *
    *
    *Office: 888.763.6797**
    http://www.shrinktheweb.com
    [email blocked] <http://shrinktheweb.com/>*
    2774 N Cobb Pkwy NW #244
    Suite 109
    Kennesaw, GA 30152

  3. #3 Posted by Duane Roumel on 28 Aug, 2013 07:49 PM

    Dean,

    To be more specific, we need to simulate a recurring charge that has
    declined, or an account that cancels because of failed payment. Is there a
    way to simulate a recurring charge without having to wait for the bill date?

  4. #4 Posted by Dean on 28 Aug, 2013 07:53 PM

    Can you use the changeBilldate API call to push back the billdate a minute or two from now and test that way? Signup a customer without payment information and set the billDate shortly after signup. The invoice will attempt to transact but there will be no payment info on file so it will fail and the customer should be canceled due to non-payment.

  5. #5 Posted by Duane Roumel on 28 Aug, 2013 07:56 PM

    We will give it a shot, thanks.

  6. #6 Posted by Marc Guyer Support staff on 29 Aug, 2013 03:07 PM

    Hi Duane -- There are two general different types of error simulation as documented here:

    http://support.cheddargetter.com/kb/api-8/error-simulation

    A real-time error occurs when updating a payment method on a subscription. If you want the error to happen on that event, you would use the 0 prefix.

    A delayed error occurs when a transaction occurs at some point in time after the payment method is updated. So, using the 9 prefix, the payment method is updated successfully without error and the next transaction event will result in the simulated error.

    Like Dean said, you can us the changeBillDate param to accelerate the next recurring invoice. You can set it to now and the transaction will occur immediately. Or, set it to some time in the future and CG's recurring engine will pick it up for processing up to 3 hours later. So, unless you use now, there is some waiting involved.

  7. Jess Pendley closed this discussion on 21 Nov, 2013 07:48 PM.

Discussions are closed to public comments.
If you need help with Cheddar please start a new discussion.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac

Recent Discussions

Recent Articles