[REFACTOR] Worldpay payments integration

[kashif-m]

Feature Description

WorldPay payments integration currently makes use of modular APIs which gives more control over the integration. This approach is not best compatible with HyperSwitch due to WP's 3DS flows - which requires sending PAN (card numbers) in multiple places. For on_session transactions, this would contribute to the added complexity since data is not stored in such transactions (or stored for ~15mins in redis cache).

Migrating to WP's standard payments API follows payment resource creation in an uniform way.

Possible Implementation

Migrate from modular APIs [ref] to standard payment APIs [ref].

Have you spent some time checking if this feature request has been raised before?

• I checked and didn't find a similar issue

Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to submit a PR?

Yes, I am willing to submit a PR!

[kashif-m]

# 2

Propagate the refusal codes as error codes in HyperSwitch.

[kashif-m]

# 3

• Make payment_method_type non-mandatory
• Fix PM filters

[kashif-m]

# 4

• Add cypress test cases

[kashif-m]

# 5

• Use automatic capture by default
• Add dynamic fields
• Bugfix - Refund list
  • Refunds list does not work for Worldpay
  • Why?
    • Refunds retrieve flow looks up for payment_attempt in DB using connector_transaction_id stored in refunds table.
    • connector_transaction_id in payment_attempt is a hashed value for Worldpay (due to it's ID length being > 128 chars)
    • Application uses ConnectorTransactionId and the value to lookup PaymentAttempt is happening using the actual ID instead of the hashed ID
  • Fix
    • Make find_by_connector_transaction_id_payment_id_merchant_id use ConnectorTransactionId instead of str
    • Lookup in DB using the value stored in that column instead of fetching actual connector's transaction ID

[kashif-m]

# 6

• Mandates
• Webhooks

[kashif-m]

# 7 Bugs

• Use 4 digit expiry year

[kashif-m]

Re-opening for #6468

[kashif-m]

# 8

Refactor

• Update username and password mapping during MCA creation on dashboard