feat(qwikcilver): add payment method eligibility check

[Aishwariyaa-Anand]

Description

Adds PaymentMethodEligibility support for Qwikcilver, and a composite endpoint that bootstraps the connector's access token before calling it.

• Qwikcilver eligibility flow (PaymentMethodService.Eligibility): performs the exact same wallet lookup Qwikcilver's GetPaymentMethod already does (GET /wallet/{wallet_number}, or by customer phone as a fallback), maps the wallet's status to ELIGIBLE (ACTIVE) / INELIGIBLE (INACTIVE), and returns the wallet's payment_method_details (balance, items) in the same response instead of a bare eligible/ineligible flag.
• Shared proto/domain changes: added connector_payment_method_id to PaymentMethodServiceEligibilityRequest and payment_method_details to PaymentMethodServiceEligibilityResponse. Both are additive/optional, so the existing BNPL eligibility usage (Tamara) is unaffected.
• Composite flow (CompositePaymentMethodService.Eligibility, POST /composite/payment_methods/eligibility): follows the same access-token-bootstrap + forward pattern as /composite/payment_methods/get — auto-bootstraps the connector's session token via MerchantAuthenticationService.CreateServerAuthenticationToken (only when the connector requires one and the caller hasn't already supplied one), splices the resulting token into the inner PaymentMethodService.Eligibility request via state.access_token, and forwards. This lets callers hit a single endpoint instead of manually calling /payments/server_authentication_token first.

Motivation and Context

Additional Changes

• This PR modifies the API contract
  • crates/types-traits/grpc-api-types/proto/payment.proto (PaymentMethodServiceEligibilityRequest/Response)
  • crates/types-traits/grpc-api-types/proto/composite_services.proto (new CompositePaymentMethodService.Eligibility RPC)
  • crates/types-traits/grpc-api-types/proto/composite_payment.proto (new CompositePaymentMethodEligibilityRequest/Response messages)
• This PR modifies application configuration/environment variables

How did you test it?

composite eligibility

curl --location 'http://localhost:8000/composite/payment_methods/eligibility' \
--header 'Content-Type: application/json' \
--header 'x-connector: qwikcilver' \
--header 'x-connector-config: {"config":{-}}}' \
--header 'x-merchant-id: JUSPAYUAT' \
--header 'x-tenant-id: public' \
--data '{
    "connector_payment_method_id": "4999771007702947",
    "amount": {
        "minor_amount": 1000,
        "currency": "USD"
    },
    "order_details": []
}
'

Response

{
    "access_token_response": {
        "access_token": "-",
        "token_type": "Bearer",
        "expires_in_seconds": 1200,
        "status": "OPERATION_STATUS_SUCCESS",
        "status_code": 200
    },
    "eligibility_response": {
        "eligibility": "ELIGIBLE",
        "status_code": 200,
        "raw_connector_request": "-",
        "raw_connector_response": "-",
        "typed_connector_response": "{\"Wallet\":{\"WalletNumber\":\"*** alloc::string::String ***\",\"ExternalWalletId\":\"*** alloc::string::String ***\",\"WalletPin\":\"*** alloc::string::String ***\",\"Status\":\"ACTIVE\",\"TrackData\":null,\"BarCode\":null,\"WalletProgramGroupName\":\"PAWC-AFG Payblue Wallet UAE\",\"WalletHolderName\":\"*** alloc::string::String ***\",\"Balance\":2339.68,\"Notes\":\"Wallet AFG\",\"Card\":null,\"Customer\":{\"CustomerType\":\"WALLETCUSTOMER\",\"Salutation\":\"MR\",\"Firstname\":\"*** alloc::string::String ***\",\"LastName\":\"*** alloc::string::String ***\",\"PhoneNumber\":\"*** alloc::string::String ***\",\"Email\":\"********@PINELABS.COM\",\"DOB\":\"*** alloc::string::String ***\",\"AddressLine1\":\"*** alloc::string::String ***\",\"AddressLine2\":\"*** alloc::string::String ***\",\"ExternalCustomerId\":null}},\"CurrentBatchNumber\":17732929,\"Notes\":\"Wallet AFG\",\"ApprovalCode\":\"147662602\",\"ResponseCode\":0,\"ResponseMessage\":\"Transaction successful.\",\"TransactionId\":1786716858212010000,\"TransactionType\":\"WALLET GET\",\"ErrorCode\":null,\"ErrorDescription\":null}",
        "response_headers": {
            "content-length": "1160",
            "connection": "keep-alive",
            "date": "Fri, 14 Aug 2026 14:14:18 GMT",
            "cache-control": "no-cache",
            "expires": "-1",
            "x-content-type-options": "nosniff",
            "access-control-allow-origin": "*",
            "access-control-expose-headers": "WWW-Authenticate",
            "pragma": "no-cache",
            "api-supported-versions": "2.0",
            "content-type": "application/json; charset=utf-8",
            "server": "Microsoft-IIS/10.0",
            "strict-transport-security": "Strict-Transport-Security: max-age=31536000; includeSubDomains"
        },
        "payment_method_details": {
            "details": {
                "Wallet": {
                    "wallet_account_id": "4999771007702947",
                    "wallet_pin": "",
                    "wallet_status": "ACTIVE_WALLET",
                    "wallet_holder_name": "MR. PRASHANT M",
                    "balance": 233968,
                    "product_id": "PAWC-AFG Payblue Wallet UAE",
                    "items": []
                }
            }
        }
    }
}

[JeevaRamu0104]

amount.currency is the order currency, but it drives convert_back on the wallet's balance. GetPaymentMethod (:1178) and CreatePaymentMethod (:1113) read the same envelope via currency_from_feature_data. A JPY order against the AED wallet from your repro turns 2339.68 into 2340 instead of 233968, so /get and /eligibility report different balances for one wallet.

Suggested change

	let currency = data.request.amount.currency;
	let currency =
	currency_from_feature_data(data.request.connector_feature_data.as_ref());

Some(currency) at :1257 then becomes just currency.

[Aishwariyaa-Anand]

this is not required in connector_feature_data, passing it in the amount field itself

[JeevaRamu0104]

Only amount.currency is read here — amount.minor_amount never enters the verdict, so an ACTIVE wallet with a zero balance comes back ELIGIBLE for any order total. Is that intended? For a stored-value instrument I'd expect the balance check to happen here rather than being left to the caller.

[Aishwariyaa-Anand]

we will only check for wallet eligibility and not amount cause the payment can also be performed via split payments