-
Notifications
You must be signed in to change notification settings - Fork 1
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
BACs payment status support #7
Comments
There are also half a dozen new BACs webhooks, and four new BACS endpoints (two GET and two PUT). |
Are these all new additions to the Starling payments API? We don’t need to do anything with BACS |
Yes, these are all new. I'm trying to keep up with any changes to the API, so we don't get any surprises. It is something to be aware of. We may, for example, miss some incoming funding payments if we are not watching the BACS webhooks. |
We can’t accommodate changes at this stage. Otherwise it’s an ever-moving target. Make a note of the webhook/API changes but there should be no coding changes at this stage. |
…e and retrieval. Not tested yet. Four new endpoints to set up and manage BACS mandates. Some refactor of common properties into traits will help simplfy code a lot, in partciaular the accountUid and addressUid proeprties.
The webhooks have not been created yet.
Will come back to this later, with testing, objects, models.
No tests for these yet, and not yet tried against sandbox.
not yet tested or tried against sandbox.
Along with the
fasterPaymentStatus
objects returned for the payment account address, there is now abacsStatus
object with similar statuses.A new PUT method allows the BACs statuses (diectCredit and diectDebit) to be enabled and disabled.
The text was updated successfully, but these errors were encountered: