adding support for 3ds, sepa, merchant_profile, sent_address and received_address fields for fintech

[rsomavarapu-sift]

Purpose

• Add support for new Fintech API fields which can be used for various purposes in the future like feature extraction, reporting, workflow management, etc.

Technical Overview

• Support for the following API fields is added
  • $merchant_profile complex field. This field contains the fields $merchant_id, $merchant_name, $merchant_address, and $merchant_category_code. Thiis field is supported in $create_order, $update_order, and $transaction events.
  • $status_3ds, $triggered_3ds, $merchant_initiated_transaction, $sent_address, and $received_address are supported in $transaction event.
  • $shortened_iban_first6, $shortened_iban_last4, and $sepa_direct_debit_mandate are supported in $transaction event and $payment_method field

Testing Plan

• Updated unit tests

Deployment
(Once all the fintech-related changes are merged)

• Publish to Maven Central
• Create a GitHub release

Note - I will update the changelog during the last PR as it would cause conflicts now.

[natashasehgal]

Is there a reason some files are removed?

[rsomavarapu-sift]

@natashasehgal I removed those files and added all those tests in CreateOrderEventTest.java as it is the convention we are following.

[natashasehgal]

@natashasehgal I removed those files and added all those tests in CreateOrderEventTest.java as it is the convention we are following.

Thanks for making those changes along with your fintech ones!

[natashasehgal]

LGTM

[michelgoldstein]

LGTM

[vincent-sift]

LGTM