Release 2026-06-05
This targeted release brings a couple of platform and product improvements to the Getpaid experience.
Platforms can now access more seller context directly from the Applications API, and the Getpaid Dashboard behaves more consistently on smaller screens.
The API now returns additional details, making it easier to power review, support, and lifecycle automation without extra lookups.
Richer application retrieval responses
The Applications API now returns business, applicant, and expires_at in application retrieval responses for both
onboarding and change_request applications.
This gives platforms a fuller view of who is applying, which business is being represented, and when the hosted flow expires, while keeping the response shape consistent across application types.
{
"id": "app_4fekhxdpss1et7rjp8t7rdpnw4",
"status": "initiated",
"reference": "456126",
"account": {
"id": "acc_f6m9n2q3ps8et4rjk7d1xbvw5c"
},
"business": {
"legal_name": "Test Company GmbH",
"country": "DE"
},
"applicant": {
"email": "markus.keller@garagegermany.de",
"first_name": "Markus",
"last_name": "Keller"
},
"created_at": "2026-02-03T10:00:00.000Z",
"updated_at": "2026-02-03T10:00:00.000Z",
"expires_at": "2026-02-17T10:00:00.000Z"
}
business and applicant are nullable container nodes. When business is present, all internal fields required by
the response schema are returned. When applicant is present, email is required and the name fields remain optional.
See the Applications guide for the hosted flow overview and the API reference for the full response schema.
Smoother dashboard experience on smaller screens
The Getpaid Dashboard now behaves more consistently at smaller resolutions, including tablets and smartphones, so teams get a more reliable cross-device experience when working away from a desktop.
This update helps the interface adapt better to the constraints of compact screens while keeping everyday workflows usable and predictable.