> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/online-payments/payment-actions.md). # Payment actions {% embed url="" %} Payment Provider Contracts (PPCs) are available to a given organization to process a particular payment method. Thus, PPCs create a connection between the acquirer or other payment method processors. \ Utilize Processor entity to enter the Merchant's credentials assigned by the relevant processor.\ Reuse Processors for different accounts in case the Merchant Account of the acquirer/processor supports multi-currency. ## Payment Actions Payment actions are handled through your regional portal (Verifone Central) or the API. * [Capturing authorizations](/online-payments/payment-actions/capturing-an-authorization.md) * [Canceling captures](/online-payments/payment-actions/void.md) * [Refunding transactions](/online-payments/payment-actions/refunds.md) Thus, you (the merchant) can integrate your backend systems with the Verifone API. When you handle payment actions via Verifone Central, you do not need to have an additional integration endpoint. Depending on your region and your integration method you can select the corresponding environments from [Sandbox and Production URLs](/online-payments/api-integration-methods-auth-and-endpoints.md#sandbox-and-production-urls) to perform payment actions. {% hint style="info" %} The availability of transaction actions will depend on the transaction's expiry date. {% endhint %} ## Payment Processing An organization requires to have connected (linked) processors and accounts for payment processing. Processors are available within the organization's scope. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.verifone.com/online-payments/payment-actions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.