Originally Posted by
flarmip
Same here, although I can't say I'm terribly surprised given Barclays' IT.
I thought their email was very poor. As a general principle of customer service they should have credited everyone with some token amount automatically - even if only 100 Avios - rather than just say "sorry we are a month late".
Their IT has been completely hopeless with this product, some of the worst I've seen from modern banking. Since opening the account:
- online purchases with the card are getting an authorisation popup which offers (a) an unknown phone number alongside mine - they cannot explain what it is; (b) authorise with app but the messages never arrive
- their Open Banking API is sending garbled transaction description data through its interface with other providers, eg classifying an Irish transaction as Iran, describing a 79p transaction as "7928.26", and randomly adding ",null".
Both the above have been reported, complaints lodged, complaints escalated etc, but remain unfixed.
Generally shambolic. This, plus their refusal to give me a decent credit limit because it's processed by robots not humans, is making me regret moving to Barclaycard.
UPDATE:
Just got this response from Barclaycard. Their support team has looked (for seven months) at the examples we have given of what they are sending in Open Banking, for example this description for a £2.49 payment to Apple:
"Apple.com/bill, 08001076285, 24928.26 null IRAN - APPLE.COM/BILL"
Note that they are sending "IRAN" instead of Ireland; and 24929.26 instead of 2.49.
Here's their fantastically amusing response:
" The Final Response for transactionDescription is populated based on combining 3 different description fields - transDesc1, transDesc2 and transDesc3 separated by a Delimiter (;
. Based on the review from our designers, the value populated in the "transactionDescription" does look correct as per the current API Logic. they did look to see if we were able to correct this but they found no way of being able to do this unfortunately."
In other words, they can see that they are sending three bits of data. The fact that the data is wrong is not their problem.
And we wonder why they can't process Avios on time.