# Payments

## What Is a Payment?

A payment represents a customer's transaction processed through the GetNet Global API, regardless of the payment method used (credit card, debit card, PIX, Boleto, Bizum, or other alternative payment methods).

Payments collect essential transaction details, including customer information, total amount, currency, payment method, order details, and more. Each payment can have one or more associated transactions that determine its final outcome. For a deeper understanding of transaction types and how they relate to payments, refer to the [Transactions](/en/global-api/sep-api/core-concepts-api/transactions) page.

## Payment Lifecycle

The following diagram illustrates the possible payment statuses and their connections throughout the payment lifecycle. Every payment has a status that follows a standardized flow, ensuring consistent functionality across all payment methods. A payment moves through a sequence of statuses until completion. The diagram below shows the potential outcomes based on transaction processing.

[DIAGRAM_PLACEHOLDER: payment-lifecycle-flow.mermaid]

### Payment Statuses

Each payment in the GetNet Global API can have one of the following statuses:

| Status | Description |
| :----- | :---------- |
| **PENDING** | Payment is being processed and awaiting a final status. May be awaiting provider confirmation, 3DS verification, or fraud screening. |
| **WAITING** | Payment is waiting for customer action or external authentication (e.g., 3DS authentication, redirect completion). |
| **APPROVED** | Payment was successfully processed and approved by the issuer. Funds are captured or available for capture. |
| **DENIED** | Payment was rejected by the issuer or payment processor (e.g., insufficient funds, card declined, fraud detection). |
| **ERROR** | A system error occurred during payment processing. |
| **EXPIRED** | Payment expired before completion (e.g., authorization timeout, payment window closed). |

After a payment is **APPROVED**, you can perform post-sale operations such as cancellations (reversals) or refunds (full or partial). These are separate API operations, not payment statuses.

For more details on status codes and transaction-level statuses, refer to the [Transactions](/en/global-api/sep-api/core-concepts-api/transactions) page and the [API Reference](https://docs.globalgetnet.com/en/products/online-payments/regional-api/swagger).

## Payments and Transactions

A payment consists of one or more transactions that determine its final outcome. When you enable additional features for your payment flow—such as 3D Secure authentication, fraud screening, or authorization-and-capture flows—these create additional transactions that become part of the payment lifecycle.

**Key relationships:**

- **Single-step payments** (purchase): One primary transaction that immediately charges the customer
- **Two-step payments** (authorize and capture): Multiple transactions—first reserving funds, then capturing them
- **Post-sale operations**: Additional transactions for cancellations, refunds, or adjustments

Each transaction within a payment has its own status that contributes to the overall payment status. For example, a payment with APPROVED status may contain multiple transactions: an approved authorization, a successful fraud screening verification, and a captured charge.

You can query all transactions associated with a payment using the [Get Transaction](https://docs.globalgetnet.com/en/products/online-payments/regional-api/swagger#tag/payment-record-management/get/dpm/hub-payment-info/v1/payments/info/{payment_id}) endpoint. This returns detailed information about each transaction, including their individual statuses, timestamps, and processing details.

## See Also

For detailed implementation guides and code examples, see the [Payment Guides](https://docs.globalgetnet.com/en/products/online-payments/regional-api?doc=payment-guides) section in the documentation. To understand transaction types and how they relate to payments, see [Transactions](/en/global-api/sep-api/core-concepts-api/transactions). For security features and compliance, see [Tokenization](/en/global-api/sep-api/core-concepts-api/tokenization), [3DS Authentication 2.0](/en/global-api/sep-api/core-concepts-api/3dsecure), [Card Verification](/en/global-api/sep-api/core-concepts-api/card-verification), and [PCI Compliance](https://docs.globalgetnet.com/en/products/online-payments/regional-api?doc=pci-compliance).