feat(payment-link): alternate text for manual captures

[mrudulvajpayee4935]

Type of Change

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

Description

Payment links will have Add Payment Method as the button text in case of manual captures payments. Payment button text is localised and will have value according to locale used.

Additional Changes

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

Motivation and Context

Payment links created with capture_method: manual - where the intention is to authorize the customer for some non zero amount, and capture the authorized amount at some later point in time. In such scenarios, the text Pay Now is incorrect as the user is not actually paying in that moment.

How did you test it?

Curl:

curl --location 'http://localhost:8080/payments' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: dev_MEIFMzxdOieBrD6NfMq5fkdKPlnh9EGSk4qgFWZ2Zv7cAR3eleriFFmTmJnfu2bI' \
--header 'Accept-Language: de' \
--data '{
    "amount": 700,
    "customer_id": "cus_5CPXeuPb98HjRkbQifzd",
    "currency": "USD",
    "payment_link": true,
    "session_expiry": 1000000,
    "return_url": "https://google.com",
    "payment_link_config": {
        "logo": "https://cdn.pixabay.com/photo/2021/08/28/08/48/deer-geface-6580415_1280.png",
        "seller_name": "Cookie Inc."
    }
}'

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

[semanticdiff-com]

Review changes with  

Changed Files

File	Status
crates/router/src/core/payment_link/payment_link_initiate/payment_link.js	2% smaller
crates/router/src/core/payment_link/locale.js	0% smaller

[kashif-m]

Give precedence to paymentDetails.payment_button_text

And use strict check (===) for equality statement, since this is JS ..

Better to use if else for readability, since we have 3 variables involved now