Overview
Test data is used to verify that QFD meets its requirements, functions correctly, and handles all configured scenarios.
Please provide ample (minimum 5 in each area) test account numbers including data for each applicable category below for both Quavo’s internal testing and your organization's testing. If the test data is aged, please advise date range so developers can find it.
All Transactions Types Applicable: | Across All Account Types Applicable: | Amounts: | Transaction Status |
Credit | Business checking | Under Auto-Pay Thresholds | Pending |
Debit | Business credit | Over Auto-Pay Thresholds | Posted |
ACH | Personal checking | Over Manager Approval Required Values | |
Check | Personal savings | ||
Zelle | Personal credit | ||
Wire | Prepaid | ||
ATM | |||
RTP | |||
P2B | |||
Bill Pay | |||
Merchant Credits |
Process
Test data typically derives from the system of record. Test data can be completely fake or sanitized production data.
QFD will complete API calls using the test customer or account data. The API will return the test transactions to allow for claim creation and testing.
If we exhaust the test accounts provided, we will request more, so please provide a substantial quantity to begin. It’s crucial to ensure that your staging environment has test information for all transaction types you intend to support.