Open BenjaminEHowe opened 6 years ago
This only applies for unknown counterparties (i.e. counterparties who aren't stored as payees). Unfortunately I'm suspecting this may not be a bug, and actually due to data protection / GDPR... Perhaps @Stephan5 can weigh in?
I’m not sure on this one. We will be overhauling the transaction API at some point in the near future to bring it in line with our new internal APIs. I will look into this and see if it is worth doing prior to that.
Thanks, @Stephan5! (also, thanks for the super-quick reply)
I'd really appreciate alpha access to "new" versions of public APIs as and when they're ready. Is there any way to sign up to this? I appreciate that YAMM isn't (and won't ever be!) an official integration, but I hope that it can be useful for a number of customers, especially more technical customers who might not trust cloud-based AISPs.
The reference is shown in the
description
, but the counterparty isn't shown. This is an issue with the Starling API. Starling have added this issue to their backlog.