For Payments product in the UK only.
Starling have a new, better API. We’re now moving over to that. This will mean a more reliable service via Starling in the future.
The current integration is highly incident prone and has caused multiple outages in our service to Starling in the last 12 months.
This breaking change will impact all clients on the Payments product in the UK.
For the Data Product please refer to this article.
Changes, Impact, and Actions to Take
The transition should be relatively seamless, ob-starling will become increasingly available in the payment provider selection screen and in our get payment providers endpoint supporting the preselected payment flow.
The transition will span across 2 months.
| Stage |
Nature |
Impact |
Client Actions |
Date |
1. ob-starling is accepted in the preselected flow |
 Backwards compatible |
N/A |
N/A |
19.06.2023 |
2. ob-starling is becoming increasingly available to a growing number of clients in the user_selected flow |
Backwards compatible |
oauth-starling will be replaced by ob-starling in the provider selection screen for PSU
|
N/A |
21.06.2023 - 09.07.2023 |
3. oauth-starling is superseded by ob-starling |
Backwards compatible |
oauth-starling will be replaced by ob-starling in v1 and v2 get providers response |
- Client should refresh their cache
- Client should verify oauth-starling is removed from their system and ready for deprecation
|
10.07.2023 -
8.08.2023 |
4. oauth-starling is no longer accepted |
 Breaking |
Payments created with oauth-starling will be rejected
|
- Ensure that the actions from the step 3 have been taken |
9.08.2023 |
If you have any questions please create a ticket on our Help Centre and we will be in touch as soon as possible.
