Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible to expose bank_reference_prefix for creditor entities? #28

Open
M1ke opened this issue May 25, 2017 · 4 comments
Open

Possible to expose bank_reference_prefix for creditor entities? #28

M1ke opened this issue May 25, 2017 · 4 comments

Comments

@M1ke
Copy link

M1ke commented May 25, 2017

Recent updates have improved data available from the API for Creditors.

However the field bank_reference_prefix is still not available. I am imagining the change to make that available would be very small, given that field is available in the JSON output on the GoCardless manage page.

@timrogers
Copy link

@M1ke Thanks for creating this issue! At the moment, bank_reference_prefix is not exposed in the public API, but rather only to Dashboard. We'll chat internally about exposing this. Out of interest, what would you want to use it for?

@M1ke
Copy link
Author

M1ke commented May 25, 2017

@timrogers We manage a large number of creditors who are all taking payments into their own accounts managed via our platform. When they set up a creditor, the creditor name becomes their default bank reference, but the people paying them are using our platform, so we change the reference to our company name to make it clearer and reduce the chance of a charge back. At present someone has to go and check each new creditor to ensure this is correct. If we had GET access we could at least automate the check, and if we could submit that field in a create action then we would be able to automate the whole process.

@timrogers
Copy link

@M1ke Thanks! We'll have a think 🤔

@jjholmes927
Copy link
Contributor

@M1ke Hey Mike! Seen this unresolved thread by chance, caught my eye as we are planning on renaming this field and exposing it via the public API so if this still relevant to you it should be available in the not too distant future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants