There was a bug in some unique cases when doing a Sofort PayIn whereby it would be prematurely failed, even though it was later successful – this has now been corrected
We’ve updated various elements of the integration with our PSP
Transaction reporting [From v2]
We’re really excited to bring a reporting feature to the API where you can export full transaction lists. We’ll slowly be rolling this out to all clients during the next week
Be able to disactive a Bank Account [From v2]
Following your feedback, we’ve added functionality to be able to disactivate a bank account – this works in just the same way as for cards (more info)
We’ve further bolstered our fraud prevention processes by enhancing our black list management for countries, IBANs and BICs
Add RepudiationId to Disputes [From v2]
To help you find the RepudiationId associated with a Dispute, we’ve add this info to the Dispute object (more info)
Add new LegalPersonType [From v2]
To respond to your feedback, we’ve added a new
LegalPersonTypecalled "Soletrader" for legal users without a registered business (more info)
Fix a problem with some 3DS payments [From v2]
In some rare cases, a user can actually be debited when doing a direct payin with 3DS that is shown as failed in the API (more info)
We’ve updated a few internal support team tools to further help them help you!
Fix for IdempotencyKey lookup
In some particular cases the IdemptotencyKey feature throws an error
Fix for Direct Payin and 3D-Secure
In certain cases the transaction status isn’t updated correctly
Performance tuning for transfers and payouts
UserId and WalletId to the reporting endpointAccountNumber - the validation service we used already required this, but there were some cases where an incorrect length was possiblePostalCode fieldTechEmails list (rather than just the first)We strive to offer you a secure payment solution, which means we review our fraud rules continuously to stay ahead of fraudsters.
Today, by default, 3D-secure is automatically triggered if a payment is more than 100EUR. In order to fight fraud more efficiently and reduce chargeback risk, the amount by default will now be set at 50EUR, or the equivalent amount in other supported currencies. As a result, 3D-secure will be triggered for all the payments of more than 50EUR.
You don't need to do anything as this will be an automatic change.
If you have any questions, please feel free to reach out to our sales team.
The change will be effective from 27th February 2017 onwards and is already effective in sandbox from today.
StatementDescriptor was not taken into account in some cases for a payin card directWalletID filter was setStatus = FAILED and ResultCode = 0019999 rather than staying as CREATEDResultCode 101106StatementDescriptor field for direct debit paymentsStatus not correctly being updated in some cases for direct debit mandatesDocumentURL returned a 404 error for mandatesContestDeadlineDate) for Disputes is now clearer (it's now at 23:59:59 instead of 00:00:00 - ie at the end of the day)Fingerprint - this value will always be the same regardless of how many times you register the same physical card, or for whichever user. We'll be adding more functionality to do with this in the future (like card unicity tools, fraud prevention and the same information for web payins).CompanyNumber which is not required at this time, but we highly recommend that you provide this informationCreditedUserId is now correctly shown for repudiation refunds