May 29, 2015 at 9:08 am /
As of now, reference numbers such as the SEPA end-to-end-ID are not supported. The SEPA end-to-end-ID is supported in most online banking platforms (in German often called “Kundenreferenz” or “Auftraggeberreferenz”).
People use this field often for order numbers or invoice numbers – or sometimes for text because they confuse it with the normal subject (“Verwendungszweck”).
The End-To-End ID should be supported both when initiating a transfer (in sepa_credit_transfers) and also in incoming SEPA payments (in transactions.transaction_type_details).
If that’s not possible, an incoming End-To-End-ID should at least be integrated into transactions.subject.
June 10, 2015 at 4:12 pm /
we have it on our to-do list. Unfortunately there are some third party services involved that have to be taken care of as well. This fact slows us a little bit down.
Nevertheless we will try to take care as soon as possible.
October 9, 2015 at 9:18 am /
(changed to support question)
April 5, 2016 at 7:50 am /
Hi, anything new on that?
April 5, 2016 at 2:37 pm /
we have this
information now and we will add this information to our sepa transactions as
There is still no way to provide the
when creating a
Though the mills of God grind slowly, yet they grind exceeding fine
April 5, 2016 at 2:49 pm /
eref will be in
transaction directly or
Keep on grinding 😉
April 5, 2016 at 2:55 pm /
Mmm, I dunno yet to be honest but since it’s only
related, I think it makes sense to add to the details – otherwise we’ll have an attribute that will be
in any other transaction types.
June 30, 2016 at 6:39 am /
Hi Igor, is the
eref already available?