Adding the property of the first transaction ID to the payment SDK

Original Publishing Date:
2020-03-05

Introduction

Due to changes in payment processing introduced by Visa and MasterCard, an update of payment method properties is required. In addition to other properties, the affected payment methods will need to pass the ID of the first transaction made by means of that payment method. The script below updates existing payment methods by searching and adding the ID of the first transaction to the list of methods' properties.

Instructions

Download OA-7315-Add_transaction_id.py to the billing application server.
Run it with the --dry-run option to determine if there is anything that need updating:
```
# python OA-7315-Add_transaction_id.py --dry-run
```
If you need to update specific payment methods, first list the available payment methods by running the script with the --list-methods option and run the script with the --methods option having specified the method names as follows:
```
# python OA-7315-Add_transaction_id.py --list-methods
# python OA-7315-Add_transaction_id.py --methods=Stripe.Token,Demo.Token
```
If it is required to entitle parameter for storing first transation ID other that 'first_transaction_id', specify it with --param-name option.
If you want to update all payment methods, run the script without any options:
```
# python OA-7315-Add_transaction_id.py
```

As a result, the script shows information about the payment methods that were found and updated. Payment methods cannot be updated if their first transactions are not found in the database. In this case, the payments made using that method will likely be declined by Visa or MasterCard. To resolve this, a customer will need to recreate that payment method. A list of payment methods that were not updated (as well as additional debug information) can be found in the script execution log file /tmp/updatepayments.log