[REFACTORE] : Connector Metadata,ApplePay and GooglePay #5086
Labels
C-feature
Category: Feature request or enhancement
S-awaiting-triage
Status: New issues that have not been assessed yet
Feature Description
Current WASM structure for the ApplePay,GooglePay and MetaData was not extendable for the additional fields.
In the case of ApplePay, all user input field changes are happening for session_token_data. With the current structure, all fields are considered text inputs. If we want to show a select box or toggle field, the connector team needs to reach out to the dashboard team for the respective changes. To avoid this dependency, the connector team will now be able to add different fields based on requirements themselves.
One such example is merchant_business_country, where the input field needs to be a select box. However, due to the current structure, the connector team is not able to add the field and needs to inform the dashboard team for the update.
In the case of GooglePay, the request structure is a bit complicated, as the user only needs to enter merchant_id, merchant_name, and gateway_merchant_id, while the rest of the data remains constant. Previously, the idea was to send these fields to WebAssembly (WASM) and construct the request there, but this created more complications in both the frontend and backend. Therefore, we decided to construct the request on the frontend itself and fetch only the input fields from WASM.
Metadata fields also have the same issue as merchant_business_country, where only text input fields are accepted with the current structure. To add a toggle or select field, the connector team needs to reach out to the dashboard team for the changes. With the modified structure, this dependency is resolved.
When does the dependency comes?
![image](https://private-user-images.githubusercontent.com/120017870/342073327-ee40a9fb-562b-42a9-9988-84042deceaf1.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk5OTAzNTksIm5iZiI6MTcxOTk5MDA1OSwicGF0aCI6Ii8xMjAwMTc4NzAvMzQyMDczMzI3LWVlNDBhOWZiLTU2MmItNDJhOS05OTg4LTg0MDQyZGVjZWFmMS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNzAzJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDcwM1QwNzAwNTlaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT01YWI2ZjM3MzQ4N2YwOWRjNWUzNDk5NWUzYWQ0NjQ0Mjk1N2JiM2I0ODBmYWY4YjIyYTk4ZmU2MGZhNWYzOWZmJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.39xqEpCPt_mKeKCQWD80hA6nAGEFkh5D9JNnvCTYAaY)
For ApplePay, current changes are happening at session_token_data. When changes need to happen at a different level, for example, if a merchant wants to change the supported_networks themselves, which is under payment_request_data, a dependency arises. They need to inform the dashboard team, which will then map the name of the field. Similar for googlePay and metadata fields.
Modified WASM structure for ApplePay,GooglePay and MetaData
Current WASM structure for ApplePay,GooglePay and MetaData
Apple Pay Request Structure for Manual
Apple Pay Request Structure for Simplified
GooglePay Request Structure
List of Apple Pay and GooglePay Connectors
Testing command
List of Apple Pay Connectors
Testing command
List of Google Pay Connectors
Testing command
List of metadata field changes
Production Connectors to Test Apple Pay And GooglePay
Production Metadata
Examples to consider klarna_region
Possible Implementation
Updated the wasm structure
Have you spent some time checking if this feature request has been raised before?
Have you read the Contributing Guidelines?
Are you willing to submit a PR?
None
The text was updated successfully, but these errors were encountered: