fix(connectors): graceful response deserialization for cryptopay

[sai-harsha-vardhan]

Summary

• Added #[serde(other)] Unknown catch-all variant to CryptopayPaymentStatus enum
• Updated ForeignTryFrom to preserve existing payment status when unknown status is received (with warning log)
• Updated webhook handler to explicitly match all enum variants (including Unknown) instead of using wildcard _
• Wrapped unused response fields in Option<Secret<String>> for forward compatibility

Changes

• crates/hyperswitch_connectors/src/connectors/cryptopay/transformers.rs
• crates/hyperswitch_connectors/src/connectors/cryptopay.rs

Checklist

• Fix 1: No #[serde(deny_unknown_fields)] present on response structs
• Fix 2: Catch-all Unknown variant added to response enum used in business logic
• Fix 3: Unused scalar fields converted to Option<Secret<String>>
• Unknown match arm preserves existing state (returns Ok(existing_router_data))

[semanticdiff-com]

Review changes with  

Changed Files

File	Status
crates/hyperswitch_connectors/src/connectors/cryptopay/transformers.rs	52% smaller
crates/hyperswitch_connectors/src/connectors/cryptopay.rs	38% smaller
crates/hyperswitch_connectors/src/connectors/nmi/transformers.rs	6% smaller

[XyneSpaces]

Review: Cryptopay Graceful Response Deserialization

✅ Approved

This PR applies the standard graceful response deserialization fixes to the Cryptopay connector:

1. Fix 2 (Enum catch-alls): Added #[serde(other)] Unknown variant to CryptopayPaymentStatus
2. Fix 3 (Opaque optional types): Wrapped unused response fields in Option<Secret<String>> for forward compatibility
3. Webhook handling: Replaced wildcard match with explicit enum variants

💡 Findings

1. Clean pattern following established conventions
The to_attempt_status method correctly takes existing status as parameter and returns it unchanged for Unknown variants, preserving existing payment state.

2. NMI connector change
The addition of Response::Unknown to the error match arm in NMI transformers appears to be a related fix - ensure this is intentional and not a cross-contamination from another branch.

3. Warning log placement
The warning log for unknown status is correctly placed inside the match arm, providing visibility when Cryptopay introduces new status values.

Summary

Severity	Count
Critical	0
Warning	0
Nitpick	0

Verdict: Clean implementation following established patterns. Ready to merge.