I’m confused about whether to use remittance_reference or remittance_text, and I want the system to prevent me from sending both.

This feature clarifies when to use remittance_reference versus remittance_text and enforces that only one can be provided per payment. It prevents ambiguous remittance information and reduces payment processing errors caused by conflicting fields.

This feature provides clear guidance on the intended use of remittance_reference and remittance_text and ensures they are mutually exclusive. When creating or validating a payment, the system checks that at most one of these fields is present. If both are supplied, the request is rejected with a validation error that explains the conflict and how to resolve it. This removes uncertainty for users who are unsure which remittance field to populate. It also standardizes outbound remittance information so downstream systems and recipients receive a single, consistent remittance value. The primary benefit is preventing accidental duplication or conflicting remittance details that can complicate reconciliation. The feature is useful in API integrations where different upstream sources may populate different remittance fields. It is also helpful in UI-based payment creation by guiding users to select the appropriate field and avoiding invalid submissions. Overall, it improves data quality, reduces failed or delayed payments due to formatting or business-rule violations, and simplifies support and troubleshooting.