Testing Your Integration

Copy

• Copy for LLM

  Copy page as Markdown for LLMs
• View as Markdown

  Open this page as Markdown
• Open in ChatGPT

  Get insights from ChatGPT
• Open in Claude

  Get insights from Claude
• Connect to Cursor

  Install MCP server on Cursor
• Connect to VS Code

  Install MCP server on VS Code

Finix offers numerous ways to test your Sandbox integration. Use the values below to test your integration. We encourage you to test these scenarios before running transactions in your Live environment.

Testing Transactions

The testing scenarios below are for testing payment transactions. These include Transfers, Authorizations, Payment Instrument responses, and more.

Testing Card Type

Use the following card numbers to trigger the respective card_type. Provide the amount in cents.

Testing AVS/CVV

Pass one of the following amount values to trigger the respective payment failure. Once a Payment Instrument is flagged with an AVS or CVV failure, it will continue to return that error. Provide the amount in cents.

Testing Name Verification

Use the following sentinel values to simulate name verification results on DUMMY_V1. If none are provided, all fields in name_verification_results return UNKNOWN. Sentinel values are not case-sensitive.

Direct Name Verification

You can perform name verification using the PUT /payment_instruments/{payment_instrument_id_verify} endpoint. Select the "Name Verification" example.

Use the first_name and last_name fields in name_verification_details to trigger a specific result. All four fields in name_verification_results return the same value.

Name Verification via Push-to-Card Eligibility Check

Verifying Push-to-Card eligibility returns name verification results.

All four fields in name_verification_results (first_name, last_name, middle_name, and name) return the same value.

Testing Failure Codes

Use the following card numbers to test failure codes. Provide the amount in cents.

After creating a Transfer with one of the card numbers below, you can see the failure_code and failure_message in the Transfer details. You can also retrieve a Transfer to check these fields.

For testing ACH return codes, refer to Testing ACH returns.

Testing Network Tokens

Use the following card numbers to set a specific network_token_state. By default, any valid card number enabled for network tokens returns an ACTIVE state. Provide the amount in cents.

Testing Account Updater

Use the following card numbers to test account updater responses. Provide the amount in cents.

Testing Refunds

Use the following card numbers to test refunds. Provide the amount in cents.

Testing Bank Account Validations

Use these specific bank codes and account numbers to test bank account validations. Provide the amount in cents.

Testing ACH Returns

Use the following bank details to trigger the respective ACH Return Code. Provide the amount in cents.

For more information about the different ACH Return Codes, see ACH Direct Debit.

• The Merchant › ready_to_settle_upon field must be PROCESSOR_WINDOW or RECONCILIATION. Currently, SUCCESSFUL_CAPTURE is not supported.
• The failure_code and failure_message are populated on the original Transfer resource.
• The tags of the new return Transfer that's created include the ACH Return Code and failure_message associated with the return.

Testing Payouts

Testing Push-to-Card

Use the following card numbers to test Push-to-Card payout responses. Provide the amount in cents.

Testing Push-to-Card Verifications

Use the following card numbers to test Push-to-Card Verification responses. Provide the amount in cents.