A verified CEP can still have a beneficiary-name difference

Keep the submitted and observed names distinct

Store the name expected by your system separately from the name reported in the verified CEP. Do not overwrite the bank’s spelling with an application profile. In GridZen, a bank-reported name is released only after signature and exact transaction binding pass. Unbound documents must not become a way to discover unrelated people’s names.

Use conservative comparisons

Spacing and case differences can be normalized without asserting a new identity. Shared words, accent differences, truncation, company abbreviations and incomplete names can require review. A partial name should not silently become a full match.

For example, a customer providing two words while the bank supplies a longer name is a review case under the conservative policy. It does not automatically establish either fraud or an exact match. Company and personal names also require different operational expectations.

Make a review action explicit

Return the observed name, comparison result and reason in separate fields. Let the authorized team ask the customer for a correction or apply its own existing review policy. Avoid making an automatic onboarding decision solely from one old payment; the evidence has an operation date and does not prove present account control.