fix(connector): [fiserv] fix metadata deserialization in merchant_connector_account

[srujanchikke]

Type of Change

• Bugfix
• New feature
• Enhancement
• Refactoring
• Dependency updates
• Documentation
• CI/CD

Description

While creating merchant connector account for fiserv , we store a field called terminal_id . If it is not present while making payment we throw 500 in this case .This PR add validation to connector metadata while creating merchant connector account for fiserv .

The existing merchant connector will not process payment as terminal_id validation is added . The following data migrations queries need to be run

If terminalId is present then convert it to terminal_id

UPDATE merchant_connector_account
SET metadata = (REPLACE(metadata::TEXT, '"terminalId"', '"terminal_id"'))::JSONB
where connector_name = 'fiserv';

and then if terminal_id is not present set terminal_id to empty string

UPDATE merchant_connector_account
SET metadata = jsonb_set(
    metadata,
    '{terminal_id}',
    '""',
    true
)
WHERE connector_name = 'fiserv'
    AND NOT metadata ? 'terminal_id';

Additional Changes

• This PR modifies the API contract
• This PR modifies the database schema
• This PR modifies application configuration/environment variables

Motivation and Context

While creating merchant connector account for fiserv , we store a field called terminal_id . If it is not present while making payment we throw 500 in this case .This PR add validation to connector metadata while creating merchant connector account for fiserv .

How did you test it?

1. if we don't pass terminal_id in metadata while creating merchant connector account .it should throw 422 error .

created a issue for postman collection : https://github.com/juspay/hyperswitch-cloud/issues/3276

Checklist

• I formatted the code cargo +nightly fmt --all
• I addressed lints thrown by cargo clippy
• I reviewed the submitted code
• I added unit tests for my changes where possible
• I added a CHANGELOG entry if applicable

[ArjunKarthik]

We have metadata in Payments request also, So here let's give the clarity of Merchant Connector account metadata. The same comment is applicable for all the places where ever you are using "metadata" for the deserialization error

[srujanchikke]

Done!