Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

🛠️ Potential Solutions

Note: this section should be short and sweet, documenting notes about different solutions that were considered during ideation. Can just be a link to a whiteboard for example. Expected outcome: one solution is chosen and documented in more detail under Proposed Solution.

✅ Proposed Solution

Description of the proposed solution.

Figma Link: https://www.figma.com/design/wEeYkRHLwLdMJHKvQJOdd0/%5BIBFEC-1795%5D-Remove-Pre-filled-Name-On-Card-field?node-id=7979-30251 ) 

Whitelabel solution:

There is a mock to automatically add data fields, to enable or disable this mock, we must use the feature flag: https://app.launchdarkly.com/intl-guest-app/dev-plk-es/features/autoFillTestCard/targeting

Remove pre-filled

  • Adjust the frontend to remove the prefill

If you want more technical details, you can read below:

 Click here to expand...

image-20240605-104429.png

Sets the field with “required“

  • Adjust the field in frontend to be required as expected in the Figma proposal

  • Then, we will need to set "required" in the missing nameOnCard fields and insert an “*” at the end of the field placeholder to inform that this field is mandatory.

Add keyboard in the Expiration Date field

  • We will add the keyboard in the expiration date field

    • currently

      image-20240611-142732.png

    • after the change

      image-20240611-142400.png

If you want more technical details, you can read below:

 Click here to expand...

image-20240611-143047.png

There will be no changes to the Payments page design or card forms at this time.

Consequences

(plus) Will decrease payment provider validation errors

(plus) It isn’t a critical change

(plus) The change will affect just IBERIA markets

(minus) Regression payment tests

(warning) Potential Challenges

List here potential challenges that have come across the opportunity definition or from the potential solutions so far.

💰 Cost

Describe any additional cost this solution may imply.

🎛️ Configuration

Include here any configuration required (Sanity, LaunchDarkly flags, etc.) required to enable the solution.

📈 Metrics

Describe the metrics that will be used to measure the solution’s success, as well as how to measure those KPIs.

🗓️ Delivery Plan

Link to the task or list of all the tasks required to deliver the solution, along with its progress.

🧑‍🚒 QA Plan

Testing scenarios. See example /wiki/spaces/EGMT/pages/4080861189.

⚠️ Call-outs

Tip: Document here any improvement or discussion regarding the feature

  • No labels