Expand description
§Terminal Models
This file contains the models and enums for working with the terminal endpoint.
Structs§
- Event
Data - The data about the event to send to the API.
For the
invoice
type, you need to pass the invoice id and offline reference:{id: invoice_id, reference: offline_reference}
. For thetransaction type, you can pass the transaction id:
{id: transaction_id}` - Fetch
Event Status Response - This struct represents the response for checking the status of an event sent to the Terminal
- Fetch
Event Status Response Data - This struct represents the data of the event status
- Fetch
Terminal Response - This struct represents the response for fetch terminal.
- Fetch
Terminal Response Data - Response Data for Fetch Terminal Route
- Fetch
Terminal Status Response - This struct represents the response for checking the status of an event sent to the Terminal
- Fetch
Terminal Status Response Data - This struct represents the data of the event status
- Send
Event Body - This struct is used to create an event body for sending an event to the paystack Terminal using the Paystack API.
This struct should be created using the
SendEventBodyBuilder
The Builder derivation allows for the automatic implementation of the builder - Send
Event Body Builder - Builder for
SendEventBody
. - Send
Event Response - This struct represents the response of sending an event to the terminal.
- Send
Event Response Data - This struct represents the data of the event response.
- Terminal
Response With NoData - Response of updating the terminal data
- Update
Terminal Body - The terminal update information to send to the API.
- Update
Terminal Body Builder - Builder for
UpdateTerminalBody
.
Enums§
- Action
Type - Represents the different action the Terminal needs to perform.
- Event
Type - Represents the different terminal event types supported by the Paystack API.
- Send
Event Body Builder Error - Error type for SendEventBodyBuilder
- Update
Terminal Body Builder Error - Error type for UpdateTerminalBodyBuilder