> This is Payabli documentation. For a complete page index, fetch https://docs.payabli.com/llms.txt — append .md to any page URL for lightweight markdown. For section-level indexes, query parameters, and other AI-optimized access methods, see https://docs.payabli.com/ai-agents.md

## v2.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](/changelog/api-changelog/2026/10/19) for more information.

### New methods

* `money_out.get_next_check_number(paypoint_id: i64, account_id: &str, options)` returns `Result<NextCheckNumberResponse, ApiError>`. `NextCheckNumberResponse::check_number` is a `String`.
* `ghost_card.delete_ghost_card(card_token: &str, options)` returns `Result<DeleteGhostCardResponse, ApiError>`. Its `response_data` has `delete_type` and `card_token` (`Option<String>`).

```rust
let next: NextCheckNumberResponse = client.money_out.get_next_check_number(285, "ACCOUNT_ID", None).await?;
let deleted: DeleteGhostCardResponse = client.ghost_card.delete_ghost_card("CARD_TOKEN", None).await?;
```

### Request changes

* `ReissueOutRequest` adds `check_number` (`Option<VendorCheckNumber>`).
* `RequestUpdateSchedule`, the request for `subscription.update_subscription`, adds `invoice_data` (`Option<BillData>`).
* `VendorData` adds `issue_1099` (`Option<bool>`).

### Vendor 1099 flag

`VendorQueryRecord`, `VendorDataResponse`, `TransferOutDetailVendor`, and `PayoutSubscriptionVendor` add the required field `issue_1099` (`Issue1099`, a tuple struct that wraps a `bool`). `AssociatedVendor`, `VCardGetResponseAssociatedVendor`, `VendorOutData`, and `GetMethodResponseResponseDataVendorsItem` add `issue_1099` (`Option<Issue1099>`).

### Payouts that paid a bill

`BillResponseData` and `BillQueryRecord2` add `transactions` (`Option<Vec<BillTransactionReference>>`). Each `BillTransactionReference` has `id_out` (`i64`) and `payment_id` (`Option<String>`).

### Card-present device details

* `TransactionQueryRecords` and `TransactionQueryRecordsCustomer` add `device_entry_mode` (`Option<DeviceEntryMode>`), `emv_auth_data` (`Option<EmvAuthData>`, with `request_emv_data` and `response_emv_data`), and `device_data` (`Option<QueryDeviceData>`).
* `DeviceQueryRecord` adds the required field `operational_status` (`DeviceQueryRecordOperationalStatus`, with the variants `Online`, `Busy`, and `Offline`), plus `app_version` and `os_version` (`Option<String>`).

Builders for `VendorQueryRecord`, `VendorDataResponse`, `TransferOutDetailVendor`, `PayoutSubscriptionVendor`, and `DeviceQueryRecord` fail with `BuildError` when a new required field is missing. Struct literals of the changed types must set the new fields.