v3.0.20
This release adds clients for the intelligent boarding API (beta) and marks the legacy boarding methods as deprecated. See October 19, 2026 for more information.
Intelligent boarding clients (beta)
Payabli::Client adds the businesses, people, paypoints, payment_methods, boarding_templates, and applications clients.
These endpoints only accept OAuth. Pass your OAuth client_id and client_secret when you create the client. See OAuth authentication and Manage API credentials.
Legacy boarding methods are deprecated
Legacy boarding will be sunset in Q2 2027. Every method on boarding and templates now has a deprecation warning in its documentation. export.export_applications was already deprecated.
Case management bank account services
BankAccountServices money_in and money_out now use the new CaseManagementMoneyInService and CaseManagementMoneyOutService types. They have the same values as MoneyInService and MoneyOutService, so existing code still works.
v3.0.19
This release adds methods to get the next check number and cancel ghost cards, a check number on reissued payouts, invoice data on subscription updates, a 1099 flag on vendors, every payout that paid a bill, and card-present device details. See October 19, 2026 for more information.
New methods
money_out.get_next_check_number(paypoint_id:, account_id:)returnsNextCheckNumberResponse, which hascheck_number.ghost_card.delete_ghost_card(card_token:)returnsDeleteGhostCardResponse. Itsresponse_datahasdelete_typeandcard_token.
Request changes
money_out.reissue_outacceptscheck_number:.subscription.update_subscriptionacceptsinvoice_data:.VendorDataaddsissue_1099.
Vendor 1099 flag
VendorQueryRecord, VendorDataResponse, TransferOutDetailVendor, and PayoutSubscriptionVendor add the required field issue_1099. AssociatedVendor, VCardGetResponseAssociatedVendor, VendorOutData, and GetMethodResponseResponseDataVendorsItem add the optional field issue_1099.
Payouts that paid a bill
BillResponseData and BillQueryRecord2 add transactions, an array of BillTransactionReference that can be nil. Each entry has id_out and payment_id.
Card-present device details
TransactionQueryRecordsandTransactionQueryRecordsCustomeradddevice_entry_mode,emv_auth_data(EmvAuthData, withrequest_emv_dataandresponse_emv_data), anddevice_data(QueryDeviceData). All three can benil.DeviceQueryRecordadds the required fieldoperational_status(DeviceQueryRecordOperationalStatus::ONLINE,BUSY, orOFFLINE), plusapp_versionandos_version, which can benil.