What the data for this category looks like
Funding source KYC data is submitted by users in the form of bank statements, tax certificates, asset ownership documents, transaction background contracts, and other materials. Data is submitted once during a single verification, with no need for continuous updates. Document formats include scanned PDFs or structured statements in Excel or CSV formats. Fields include verification subject name, capital inflow and outflow details, counterparty information, currency unit, transaction date, voucher number, and more. Currency units are typically CNY yuan or specified foreign currency denominations.
What constraints these characteristics impose on HTTP Interfaces and External Systems
Funding source data consists mostly of structured statements or unstructured vouchers. HTTP interfaces must support multi-type file uploads and content parsing. Submitted fields for a single verification include transaction details and subject information with strict compliance requirements. Interface parameter validation must cover field format, length, and enumeration value ranges. Data is only submitted during verification, with no real-time update needs. Interfaces do not require long connections or scheduled pull logic. Financial compliance rules require encrypted data transmission. Interfaces must enforce HTTPS protocol. For multi-file upload scenarios, interfaces must support batch file parameter passing.
How to configure settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
FILE_UPLOAD_ALLOWED_TYPES | application/pdf,application/vnd.openxmlformats-officedocument.spreadsheetml.sheet,text/csv | Covers common voucher and statement file formats used in funding source verification |
HTTP_REQUEST_TIMEOUT | 300 seconds | Provides sufficient processing time for large file parsing and multi-field compliance validation |
API_REQ_MAX_BODY_SIZE | 50 MB | Adapts to the conventional maximum size limit for single funding statement files |
PARSE_FIELD_STRICT_MODE | Enabled | Financial fields require strict format validation to avoid compliance risks |
CALLBACK_NOTIFY_ENABLE | Enabled | Verification results must be synchronized to external business systems |
The parameter values provided on this page are common starting points for configuration. Actual values are affected by material formats, data volume, and business rules. Specific issues require individual analysis. It is recommended to test on your own samples before finalizing settings.
Three common mistakes
- Phenomenon: The interface returns a
413 Request Entity Too Largestatus code. Cause: TheAPI_REQ_MAX_BODY_SIZEconfiguration was not adjusted, exceeding the platform's default request body size limit. - Phenomenon: No valid transaction details are parsed after uploading a funding statement file. Cause:
FILE_UPLOAD_ALLOWED_TYPESwas not configured to support Excel or CSV formats, resulting in file interception and failed parsing. - Phenomenon: Duplicate business records are generated after submitting the same verification request multiple times. Cause: No unique identifier parameter was included in the request, and interface idempotency validation logic was not enabled.
How to confirm the configuration is complete
- Upload a pre-configured funding source voucher file, verify that the parsed fields match the submitted content.
- Send a test request with compliant format parameters, confirm the interface returns a successful status code.
- Configure a callback address and complete one verification, verify that the external system receives the corresponding callback data.
- Simulate a request that exceeds the configured limits, verify that the error prompt matches expectations.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-14.