fix(revenue_recovery): Populate payment method data in record attempt flow for V2

[srujanchikke]

Type of Change

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

Description

In revenue recovery flow, when process tracker picks task , it records internal attempt first and then triggers proxy payments. Previously only customer id and psp token is required to make payment. Since recovery ml model needs all othe parameter, This PR adds support for populating payment method data in internal and external attempts .
Attempts are created in 3 scenarios

1. when external attempt is triggered by billing connectors(like chargebee,recurly) via webhooks
2. when external attempt is created by custom billing api
3. process trackers executes execute_workflow.
   These 3 scenarios are covered in this PR .

Additional Changes

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

Motivation and Context

Create payment via custom billing api, use this pr testcases #8838

1. payment method data in both external and internal attempts in DB.
2. Internal payment attempts via worldpay should be succe succeeded dded

{
    "amount_details": {
        "order_amount": 100,
        "currency": "USD"
    },
    "merchant_reference_id": "4444",
    "billing_merchant_connector_id" : "{{mca_id}}",
    "payment_merchant_connector_id": "mca_mOBlRqcT7KPPUlEBugqv",
    "error": {
        "code": "card_declined",
        "message": "Your card was declined.",
        "network_advice_code": null,
        "network_decline_code": "01",
        "network_error_message": "generic_decline"
    },
    "billing": {
        "address": {
            "first_name": "John",
            "last_name": "Dough"
        },
        "email": "[email protected]"
    },
    "attempt_status": "failure",
    "payment_method_type": "card",
    "payment_method_sub_type": "credit",
    "transaction_created_at": "2025-06-20T10:11:12Z",
    "connector_customer_id": "cus_0001",
    "connector_transaction_id": "id35987asdaaddfse",
    "primary_processor_payment_method_token": "5454540204265454",
    "action": "schedule_failed_payment",
    "billing_started_at": "2025-07-31T10:11:12Z",
    "payment_method_units": {
        "2871855923280002": {
            "card": {
                "expiry_month": "12",
                "expiry_year": "25",
                "last_four_digits": "0008",
                "card_issuer": "Chase",
                "card_network" :"visa"
            }
        }
    }
}

How did you test it?

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/utils.rs	90% smaller
crates/router/src/core/revenue_recovery/api.rs	40% smaller
crates/router/src/core/revenue_recovery/transformers.rs	7% smaller
crates/hyperswitch_domain_models/src/payments.rs	6% smaller
crates/router/src/core/revenue_recovery.rs	4% smaller
crates/api_models/src/payments.rs	1% smaller
crates/router/src/core/webhooks/recovery_incoming.rs	1% smaller
crates/hyperswitch_domain_models/src/payments/payment_attempt.rs	0% smaller
crates/router/src/core/payments/transformers.rs	0% smaller
crates/router/src/core/revenue_recovery/types.rs	0% smaller
crates/router/src/types/storage/revenue_recovery_redis_operation.rs	0% smaller
crates/router/src/types/transformers.rs	0% smaller