v1.1.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
MoneyOut.GetNextCheckNumberAsync(long paypointId, string accountId)returnsNextCheckNumberResponse, whoseCheckNumberis astring.GhostCard.DeleteGhostCardAsync(string cardToken)returnsDeleteGhostCardResponse. ItsResponseDatahasDeleteTypeandCardToken(string?).
Request changes
ReissueOutRequestaddsCheckNumber(string?).RequestUpdateSchedule, the request forSubscription.UpdateSubscriptionAsync, addsInvoiceData(BillData?).VendorDataaddsIssue1099(bool?).
Vendor 1099 flag
VendorQueryRecord, VendorDataResponse, TransferOutDetailVendor, and PayoutSubscriptionVendor add the required property Issue1099 (bool). AssociatedVendor, VCardGetResponseAssociatedVendor, VendorOutData, and GetMethodResponseResponseDataVendorsItem add Issue1099 (bool?).
Payouts that paid a bill
BillResponseData and BillQueryRecord2 add Transactions (IEnumerable<BillTransactionReference>?). Each BillTransactionReference has IdOut (long) and PaymentId (string?).
Card-present device details
TransactionQueryRecordsandTransactionQueryRecordsCustomeraddDeviceEntryMode(string?),EmvAuthData(EmvAuthData?, withRequestEmvDataandResponseEmvData), andDeviceData(QueryDeviceData?).DeviceQueryRecordadds the required propertyOperationalStatus(DeviceQueryRecordOperationalStatus, with the valuesOnline,Busy, andOffline), plusAppVersionandOsVersion(string?).
Code that creates VendorQueryRecord, VendorDataResponse, TransferOutDetailVendor, PayoutSubscriptionVendor, or DeviceQueryRecord objects without setting the new required properties, such as tests and mocks, no longer compiles. Code that only reads them isn’t affected.