v1.0.22
This release includes breaking changes. It corrects the organization details types to match the API, renames the ticket amount properties on paypoint credentials, and adds an organizations client for the intelligent boarding API (beta). See October 20, 2026 and October 22, 2026 and October 27, 2026 for more information.
Basic organization details return a response envelope
organization->getBasicOrganization and organization->getBasicOrganizationById now return ?GetBasicOrganizationResponse instead of ?OrganizationQueryRecord. The organization details are in $responseData, alongside $isSuccess and $responseText.
Organization details types match the API
OrganizationQueryRecord changes these property types:
$billingInfois now?InstrumentResponseinstead of?Instrument.InstrumentResponsehas$achAccount,$achRouting,$billingAddress,$billingCity,$billingCountry,$billingState, and$billingZip(?string).$contactsis now an array ofContactsResponseinstead ofContacts.ContactsResponsehas$contactName,$contactEmail,$contactTitle, and$contactPhone.$orgLogois now?string, the logo’s URL, instead of?FileContent.
It also adds $orgFavicon (?string), the URL of the organization’s favicon. The property names are unchanged, but their JSON names now match the PascalCase names the API returns, such as OrgId and BillingInfo.
Ticket amount properties renamed
PayabliCredentialsPascal renames $maxTicket to $maxticket and $minTicket to $minticket (?float), and the constructor keys to match.
Organizations client (beta)
PayabliClient adds $organizations, with listOrganizations, createOrganization, getOrganization, and updateOrganization. createOrganization takes CreateOrganizationWithInlineBusiness, CreateOrganizationWithBusinessReference, or CreateOrganizationAllFields. The methods return envelope types, such as PaypointDetailEnvelope. These endpoints only accept OAuth. See OAuth authentication.
Other changes
MethodsListOutadds$rtpand$wire(?bool).PaypointSummaryResponseadds$externalId(?string).