# Transactions ## Authorization - [POST /transactions/authorization](https://docs.shift4.com/apis/payments-platform-rest/openapi/transactions/transactionsauthorization.md): Used to request processor approval for an authorization. If the invoice number already exists, the amount requested will be compared to the approved amount on file, and Shift4 will request approval for the additional amount only. If approved, an updated transaction will be displayed in Lighthouse Transaction Manager. This step does NOT close and capture the funds, only authorizes the payment request. - Host Direct - Locally Installed UTG - Commerce Engine For On Premise - Commerce Engine For Cloud See the Integration Methods and URLs Section sections of the Development Quick Start guide for details regarding each processing option. See the JSON Body Schemas for more details on the various JSON body formats. ## Capture - [POST /transactions/capture](https://docs.shift4.com/apis/payments-platform-rest/openapi/transactions/transactionscapture.md): Used to close out an existing authorization request. If the invoice number already exists, the amount requested will be compared to the approved amount on file, and Shift4 will request approval for the additional amount only. If approved, the authorization will be converted to a sale transaction and be ready to be batched. For Restaurant industry, review Restaurant Authorization and Settlement Flow - Host Direct - Locally Installed UTG - Commerce Engine For On Premise - Commerce Engine For Cloud See the Integration Methods and URLs Section sections of the Development Quick Start guide for details regarding each processing option. Please note that if you are tokenzing your credit card information outside of Shift4, authorizing and capturing a payment is not available unless you store the tokenized value from Shift4 from an authorized payment request and use this token in the subsequent capture request. ## Sale/Purchase - [POST /transactions/sale](https://docs.shift4.com/apis/payments-platform-rest/openapi/transactions/transactionssale.md): Used to request processor approval for an authorization and capture in one request. If the invoice number already exists, the amount requested will be compared to the approved amount on file, and Shift4 will request approval for the additional amount only. If approved, a new sale transaction will be displayed in Lighthouse Transaction Manager and be ready to be batched. - Host Direct - Locally Installed UTG - Commerce Engine For On Premise - Commerce Engine For Cloud See the Integration Methods and URLs Section sections of the Development Quick Start guide for details regarding each processing option. See the JSON Body Schemas for more details on the various JSON body formats. ## Refund - [POST /transactions/refund](https://docs.shift4.com/apis/payments-platform-rest/openapi/transactions/refund.md): This function can be used to refund a transaction for either the full or a partial amount. - Host Direct - Locally Installed UTG - Commerce Engine For On Premise - Commerce Engine For Cloud See the Integration Methods and URLs Section sections of the Development Quick Start guide for details regarding each processing option. See the JSON Body Schemas for more details on the various JSON body formats. ## Invoice Information - [GET /transactions/invoice](https://docs.shift4.com/apis/payments-platform-rest/openapi/transactions/getinvoice.md): Used to request the status (e.g., approved, declined, error, referral, etc.) for a specific invoice; it is primarily used after a timeout or error has occurred. Voided or batched and settled invoices will return an “Invoice Not Found” error. For more information, see the Timeouts and Communication Failures section. - Host Direct - Locally Installed UTG - Commerce Engine For On Premise - Commerce Engine For Cloud See the Integration Methods and URLs Section sections of the Development Quick Start guide for details regarding each processing option. ## Void - [DELETE /transactions/invoice](https://docs.shift4.com/apis/payments-platform-rest/openapi/transactions/void.md): Used to void and reverse an invoice. This will attempt to reverse the transaction with the processor and will mark the transaction as voided in Shift4's Gateway. - Host Direct - Locally Installed UTG - Commerce Engine For On Premise - Commerce Engine For Cloud See the Integration Methods and URLs Section sections of the Development Quick Start guide for details regarding each processing option. ## Manual Authorization - [POST /transactions/manualauthorization](https://docs.shift4.com/apis/payments-platform-rest/openapi/transactions/manualauthorization.md): This function is used to request authorization in an offline scenario, which means that Shift4 will not seek processor approval. An authorization code should be included in this request if the amount being submitted in the request is greater than the authorization amount currently on file. - Host Direct - Locally Installed UTG - Commerce Engine For On Premise - Commerce Engine For Cloud See the Integration Methods and URLs Section sections of the Development Quick Start guide for details regarding each processing option. See the JSON Body Schemas for more details on the various JSON body formats. ## Manual Sale - [POST /transactions/manualsale](https://docs.shift4.com/apis/payments-platform-rest/openapi/transactions/manualsale.md): This function is used to request authorization and a sale in an offline scenario, which means that Shift4 will not seek processor approval. An authorization code should be included in this request if the amount being submitted in the request is greater than the authorization amount currently on file. For Restaurant industry, review Restaurant Authorization and Settlement Flow - Host Direct - Locally Installed UTG - Commerce Engine For On Premise - Commerce Engine For Cloud See the Integration Methods and URLs Section sections of the Development Quick Start guide for details regarding each processing option. See the JSON Body Schemas for more details on the various JSON body formats. ## Upload Signature - [POST /transactions/signature](https://docs.shift4.com/apis/payments-platform-rest/openapi/transactions/postsignature.md): This function is used to upload the captured signature to an existing invoice in Shift4's Gateway. - Host Direct - Locally Installed UTG See the Integration Methods and URLs Section sections of the Development Quick Start guide for details regarding each processing option.