# February 17, 2022¶

Corefy versions:
1.150, 1.149, 1.148, 1.147, 1.146, 1.145, 1.144, 1.143, 1.142, & 1.141

by Dmytro Dziubenko, Chief Technology Officer

Cheery Greetings from the Corefy team!

## List of changes¶

#### Added refunded and charged back amounts to the Payment invoice overview¶

From now on, there are extra Amounts parameters displayed only for refunded and charged back transactions. As their names imply, parameters inform about the partially or wholly returned amount.

You can find them in the Payment invoice overview in the Corefy Dashboard and the Payment overview in the Merchant Portal.

#### Expanded transaction logs¶

We've extended the information value of transaction logs and added an action attribute that notifies about the called API endpoint and a source attribute based on a source of the API request.

#### Deprecated the Optimal routing strategy¶

As we announced in the previous release notes, as a part of the refactoring process, we've deprecated the Optimal strategy in all existing payout schemes and card payment schemes and replaced it with the Random.

We also need to mention that adding the Blank strategy to routing deletes all other strategies in the group, so use it for a complete stop of processing if related branch conditions are met.

#### Updated customer data format in connectors according to providers' requirements¶

It's a follow-up to the previous customer entries' update. Since the data format and naming expected by various PSP may differ, we've gradually updated existing connections to synchronise formats of transferred customer data attributes with providers' expectations.

#### Additional validation for the fee setup¶

Corefy has various connected exchange rate sources automatically updated and used in transaction processing if the recipient's currency and the sender's currency don't match. You can view the complete list in the appropriate dashboard section.

But there are possible cases when we obtain from the resource a value that with fee subtraction may result in a zero or negative one. So, we've added extra validation to rate schemes rules set up to prevent such an occurrence.

And if it does happen during processing due to a rate source glitch and the final estimated rate becomes equal to or less than zero, we'll fail a transaction with the amount_conversion_error resolution.

### Dashboard improvements¶

Small but pleasant additions to the filters' functions:

• from now on, there is a badge near the used filter's name,
• and the In operator is the default when you set the filter's parameters up.

#### Removed the +New button from the Payment gateway section¶

We did some refactoring and found that no one needs it there. An if you want to create a payment using the Dashboard, it's better do it with payment invoice creation in the Transaction section.