Improve payout validation

• Effective Date: 2026-08-12 (UTC+8)
• Scope: BaaS / Payout / Payee Management

[API] Create a payee

[API] Update a payee

This update comprehensively tightens the field validation rules for the OpenAPI v1 payee module to prevent edge-case or dirty data from causing downstream submission failures. The system has introduced strict field length and character set limits (e.g., for names, account numbers, routing numbers) and enabled deep nested validation for address fields. Meanwhile, the bankAddress field has been updated to be truly optional.

• Please note that the update payee endpoint (PUT) uses full replacement logic; if bankAddress is omitted in the request, the system will explicitly clear the existing bank address stored in the database. For detailed lengths, character set requirements, and troubleshooting guides for all fields, please refer to our latest Payout Validation Rules Guide.

[API] Submit a payout

To improve actual payout success rates, we have introduced a strict upfront pre-validation mechanism specifically for the va_005 (Zenus) channel during payout creation. When a payout is routed to the va_005 channel, the system will execute 20 granular field-level checks (including name boundaries, SWIFT character sets, and dynamic routing number validation based on the payment scheme) before order creation. If pre-validation fails, the endpoint will directly return a 400 error with the original English error message, and no payout order will be created. This logic does not affect payouts via other channels, and existing retry and idempotency behaviors remain unchanged. For the complete list of pre-validation rules, please refer to our latest Payout Validation Rules Guide.

Thank you for choosing DogPay! If you encounter any issues or need assistance during integration, please feel free to reach out to the technical support team.