Skip to content Skip to main navigation Skip to footer

Testing Guidelines

Before testing, follow the steps outlined in the Basic Configuration article to install and authorize the app, set up user permissions, and set up payment methods. 

Follow the steps listed below to test payment methods configured in Opero Payments:

  1. Set the Payment Method details to Active=True and Test Mode = True
  2. Authorize the payment connector.
    1. Quickbooks:
      1. Create a Quickbooks Sandbox Company: https://developer.intuit.com/app/developer/qbo/docs/develop/sandboxes/manage-your-sandboxes
      2. Click the “Connect Quickbooks” link and sign into your Quickbooks sandbox company.
      3. Note that you can only use test mode with a sandbox company. It is not possible to use test mode with a production QB account (there will be an error).
    2. Stripe:
      1. Enter test API keys. See the “Payment Method Fields for Stripe Record Type” section of Basic Configuration Article for more information.
  3. Go to the Invoices tab and create an Invoice record.
  4. Add line items or create a fixed price invoice.
  5. Click the Pay Invoice URL link on the invoice record.
  6. Enter mock credit card or bank account information for the payment method that you are testing.
    1. Test Quickbooks Credit Card (Visa): 4112344112344113 (any CVC, any future date)
    2. Test Stripe Credit Card (Visa): 4242424242424242 (any CVC, any future date)
    3. Test Quickbooks ACH:
      1. Routing number: 322079353
      2. Account number: 11000000333456781
  7. When payment is submitted, the Payment record should be created related to the Invoice with proper status and also exist in the payment gateway used.
  8. Payment Customer record should be created and set on Invoice and Payment record.

Additional Testing Information

Stripe: https://stripe.com/docs/testing
Quickbooks: https://developer.intuit.com/app/developer/qbpayments/docs/workflows/test-your-app

0 Comments

There are no comments yet

Leave a comment

Your email address will not be published. Required fields are marked *