Create a gift card transaction
Records a credit or debit against a specific gift card and moves its balance by the amount. Supply an idempotency key so a retry returns the transaction already recorded rather than moving the balance twice.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Body
Amount to be added or removed from the gift card
^-?[0-9]+(\.[0-9]+)?$"199.99"
Idempotency key to avoid duplicate transactions. Only one transaction may exist with a given idempotency key. Subsequent requests with the same idempotency key will return the data persisted in the database.
The kind of transaction. An API client may only send manual_adjustment; the other types are recorded at the point of sale.
book_transfer, funding_from_payment, manual_adjustment, order_payment Description to write alongside the transaction
ID of the employee responsible. Only a register sends one, and it is required there; a back-office session records the signed-in user, and an API credential records itself.
ID of the checkout this transaction is tied to, from the transactions resource. Only a register sends one.
ID of the store the transaction belongs to. Optional: name a store to attribute the adjustment to it, or omit it for one that is not tied to a store.
^[0-9]+$Response
Gift card transaction created successfully.
One credit or debit on a gift card. The ledger is append-only, so a transaction is never edited or removed once recorded; a correction is another transaction.
Unique identifier for the record.
Money the transaction moved on the card. A positive amount adds funds; a negative amount spends them.
^-?[0-9]+(\.[0-9]+)?$"199.99"
ID of the API credential that recorded the transaction. Null when a person did.
When the record was created.
Note written alongside the transaction, such as why an adjustment was made.
When the transaction took effect. A sale carries the time it was completed at the register, so this can be earlier than created_at, which is when the transaction was recorded on the ledger.
ID of the employee who took the transaction at a register, or null when it was made in the back office or by an API credential.
^[0-9]+$Key supplied when the transaction was created, unique within the banner. Sending the same key again returns the transaction already recorded rather than moving the balance twice.
ID of the checkout this transaction is tied to, from the transactions resource. Null when the transaction is not tied to a checkout.
ID of the store where the transaction took place. Null for a transaction not tied to a store, such as a back-office adjustment.
^[0-9]+$What produced the transaction: funds loaded onto the card, the card spent on a sale or restored by a refund, or a back-office adjustment.
book_transfer, funding_from_payment, manual_adjustment, order_payment When the record was last changed.
ID of the back-office user who made the transaction. Null for a transaction taken at a register or by an API credential.
^[0-9]+$