# Glossary

### authorize (authorization)

The initial step in payment processing, where the issuing bank verifies the buyer's funds and places a hold on the authorized amount. No funds are transferred at this stage; however, the amount is earmarked for the transaction to proceed.

### **cancel URL**

The URL that redirects the user if they cancel the transaction, taking them back to the merchant’s site with a cancellation message.

### capture (capture transaction)

The process of finalizing an authorized transaction, where the reserved funds are officially transferred from the buyer’s account to the merchant’s account. Capture confirms the completion of payment, allowing funds to move to the merchant.

### **Extra Data**

Additional information included with a transaction for customization, tracking, or reporting purposes. It may contain optional data such as order ID, customer code, notes, or other merchant-specific details.

### **IPN URL (Instant Payment Notification URL)**

The URL that receives automated notifications from the payment system regarding transaction status (such as confirmation or cancellation), enabling real-time order status updates for the merchant.

### isAutoCapture <a href="#isautocapture" id="isautocapture"></a>

A parameter in a payment system that indicates whether a transaction should be automatically **captured** immediately after it is **authorized**.

When **isAutoCapture** is enabled (set to "true"), the transaction proceeds directly to capture right after authorization. This means that the funds are transferred from the buyer’s account to the merchant’s account automatically, without requiring manual processing. Auto-capture simplifies the payment process and is commonly used for transactions where goods or services are provided instantly, such as online purchases for digital goods.

If **isAutoCapture** is disabled (set to "false"), the transaction requires **manual capture**, allowing the merchant to confirm before funds are collected. &#x20;

### isUseOTP

A parameter in a payment system that indicates whether a transaction requires **OTP (One-Time Password)** authentication.

When **isUseOTP** is enabled (set to "true"), the transaction will prompt the user to enter an OTP, typically sent via SMS or a secure app, to verify their identity. Requiring an OTP adds an additional layer of security to prevent fraud and ensure that the transaction is being carried out by the legitimate account or cardholder.

If **isUseOTP** is disabled (set to "false"), the transaction does not require OTP, relying instead on other  authentication methods. This setting is often applied for low-risk transactions or when a seamless checkout experience is prioritized.

### refund

The return of funds to the buyer after a transaction has been captured and settled. Refunds are commonly issued for returns or service issues, and they may take additional processing time, depending on the payment system and banking networks.

### **result URL**

The URL that redirects the user after a transaction is completed (success or failure) to allow the merchant to display the transaction outcome.

### reverse (reversal)

The process of nullifying a transaction, returning held or debited funds to the buyer's account. Reversals are typically used to correct errors or resolve invalid transactions without completing the full transaction lifecycle.

### settlement

The final reconciliation step in payment processing, where captured transactions are processed, cleared, and funds are transferred to the merchant’s bank. Settlement ensures that the merchant receives the funds, typically occurring in batch processing cycles.

### void

A transaction cancellation action that stops an authorized transaction before it is captured. When voided, the authorization hold is lifted, and no funds are moved from the buyer’s account to the merchant.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.galaxypay.vn/upc/payment-gateway/appendix/glossary.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.