Welcome to Blackthorn!

Guides    

Introduction

When setting up Blackthorn | Payments, we suggest you connect your Payment Gateway in Test Mode so that you can create test Transactions, Payment Methods, and Customers.

  • In order to create successful test records in Salesforce, you must use the card and ACH numbers below and process through a test mode connected Payment Gateway.

Stripe

Stripe API Version

Want to test the latest Stripe API version before making the switch in your dashboard? Now define the latest version number on the Payment Gateway record, and you can verify that all the updates with the latest versions work with your current process in Salesforce.

An example of a version value is 2020-03-02. As seen here in Stripe's docs.

Testing Stripe Cards

Real card information cannot be used in test mode. Instead, use the following test card number, a valid expiration date in the future, and any random CVC number to create a successful Payment Method and Transaction.

  • Card number: 4242424242424242

This number will create a successful card Payment Method that can be used to capture, authorize, and refund Transactions.

Note
Additional card numbers can be found in Stripe's testing documentation.


Testing Stripe ACH Bank Accounts

Real bank account information cannot be used in test mode. Instead, use the following test bank account numbers to create an ACH Payment Method and Transaction.

Successful ACH Payment Method

  • Bank account number: 000123456789

  • Routing number: 110000000

  • Account holder type: Either option

After creation and with the newly created Payment Method's Status = "Pending", enter the micro-deposit amounts:

  • Micro-Deposit One: 32

  • Micro-Deposit Two: 45

This Payment Method is now Valid and can be used to capture and refund Transactions.

Failed ACH Payment Method

  • Bank account number: 000111111116

  • Routing number: 110000000

  • Account holder type: Either option

This Payment Method is invalid and the error message will populate in the Stripe data fields.

Note

  • If you want to test failed micro-deposit verifications, enter any two numbers besides 32 and 45.

Testing for Specific Responses and Errors

The test cards below can be used to create a Payment Method that produces a specific response.

  • Card number: 4000000000000127

When trying to create a Payment Method with this card number, an error will be thrown about a incorrect CVC code. The error message will populate in the Stripe data fields.

  • Card number: 4000000000000341

A Payment Method with this card number will be Valid, but when capturing a Transaction with this Payment Method, it will fail. The error message will populate in the Stripe data fields.

Additional testing for specific responses and errors can be found here.


Disputes

In test mode, you can use the test card below to simulate a disputed transaction:

  • Card number: 4000000000000259

A Payment Method with this card number will be Valid, but when capturing a Transaction with this Payment Method, a Dispute record will be created.

Test Winning a Dispute

  • Enter the words "winning_evidence" in the Additional Information field on the Dispute Evidence record.
    This will simulate the dispute being won and the funds being returned to your account as an adjustment Transaction.

Test Losing a Dispute

  • Enter the words "losing_evidence" in the Additional Information field on the Dispute Evidence record.
    The dispute is closed and marked as lost. Your account is not credited.

Authorize.net

Testing Authorize.net Cards

Real card information cannot be used in test mode. Instead, use the following test card number, valid expiration date in the future, and any random CVC number to create a successful Payment Method and Transaction.

  • Card number: 4111111111111111

This number will create a successful card Payment Method that can be used to capture, authorize, and refund Transactions.

Note
Additional card numbers can be found in Authorize.net's testing documentation.

Testing Authorize.net ACH Bank Accounts

Real bank account information cannot be used in test mode. Instead, use the following test bank account numbers to create an ACH Payment Method and Transaction.

Successful ACH Payment Method

  • Bank account number: 000123456789

  • Routing number: 122105812

  • Account holder type: Either option

Note: For testing purposes, eCheck.Net transactions under $100 will be accepted. To generate a decline, submit a transaction over $100. A monthly limit of $5000 is also configured in the sandbox. If you exceed this amount, your eCheck transactions will fail with a "This transaction has been declined." error message.

Testing for Specific Responses and Errors

Create a Payment Method using the following zip code to generate a decline Transaction.

  • ZIP Code: 46282 - This transaction has been declined.
  • ZIP Code: 46205 - The transaction has been declined because of an AVS mismatch. The address provided does not match billing address of cardholder.

To generate a decline for ACH, submit a transaction over $100.

Create two PM with the same name and email address to generate A duplicate record with ID [auth.net id] already exists error for the second PM.


PayPal

Test Card Number

Real card information cannot be used in test mode. Instead, use the following test card number to create a successful Payment Method and Transaction.

  • Card number: 4755007800273033
  • Expiration Date: 05/2022
  • CVV: 105

Spreedly

Spreedly has included test data in their documentation to help with your initial integration. This includes test credit card numbers and bank account values. We've provided a couple below. Check out the full list here.

Testing Spreedly Cards

Visa Credit Card

  • Card Number: 4111111111111111

Testing Spreedly ACH Bank Accounts

Bank Account

  • Routing Number: 021000021
  • Account Number: 9876543210

Deleting Test Data

Stripe

  • Navigate to your Dashboard.

  • Turn on "View test data" switch (left-hand column).

  • Click "Business settings" (left-hand colum)

  • Select Data

  • Next to Test data, click "Delete all test data..."

  • Click Delete Now.

Salesforce

Whether you are in a Production or Sandbox Org, you will need to temporarily deactivate all triggers so that you can delete Transaction, Payment Method, and Stripe Customer records.

  • Navigate to Custom Settings.

Lightning/Classic: Setup | In the Quick Find type in and select "Custom Settings.

  • Click "Manage" next to Blackthorn | Payments Triggers".

  • Edit.

  • Check the "Disable all Triggers" checkbox.

  • Save.

  • Delete all your test data. Then come back to Custom Setting and UNCHECK "Disable All Triggers".

Updated 6 months ago


Testing


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.


Have questions or need help?

Please contact us. Our team can help.