Uruguay
Rates
Uruguay has the following main IVA categories:
- Standard: 22%
- Reduced: 10%
- Exempt: 0%
Example with a Standard category value:
"rates": [
{
"key": "iva",
"value": 22.0
}
]"rates": [
{
"key": "iva",
"value": 22.0
}
]Regulation Code
regional_regulation_code field when the payment must be evaluated under a supported regional regulation or tax benefit code. This field identifies the applicable law code during processing. When you send a recognized code, Getnet applies the corresponding discount or special treatment according to the processing rules.The following law codes are currently supported:
| Code | Applies to |
|---|---|
17934 | Credit and debit cards |
19210 | Debit cards only |
regional_regulation_code when the transaction is not eligible for a regional tax benefit or does not require special regulatory treatment.The field accepts an enriched structure with the regulation code and its related invoice:
"regional_regulation_code": [
{
"code": "17934",
"invoice": "846352"
}
]"regional_regulation_code": [
{
"code": "17934",
"invoice": "846352"
}
]Invoice handling
invoice value identifies the invoice, receipt, or internal fiscal document tied to the transaction. It provides traceability between the payment and the fiscal document related to the Uruguay tax benefit flow.invoice field is optional:- When you send an
invoice, Getnet persists the value exactly as provided. - When you omit it, Getnet fills the field with the first 9 digits of the value sent in
order_id.
invoice is informational only. It carries no fiscal validity, no legal binding, and no relationship with the Uruguayan government or any fiscal authority. It serves internal traceability only, and it does not replace any fiscal declaration you are required to file.The following validation rules apply:
| Rule | Detail |
|---|---|
| Format | Up to 9 characters. Alphanumeric is accepted; numeric is preferred. |
| Quantity | One invoice per transaction. |
| Content | Must reference a real invoice, receipt, or internal unique identifier. Do not send fictitious or generic values. |
Spain
Introduction to PSD2 and Strong Customer Authentication (SCA)
- Online card payments
- Access to account information
- Bank transfers initiated through electronic channels SCA is mandatory unless a valid exemption is applied and accepted by the card issuer.
What is Strong Customer Authentication (SCA)?
Under PSD2, SCA requires that authentication be based on at least two of the following independent factors:
- Knowledge: something the user knows (e.g., password or PIN)
- Possession: something the user has (e.g., mobile device or hardware token)
- Inherence: something the user is (e.g., fingerprint or facial recognition) This is commonly known as two-factor authentication (2FA). The goal is to prevent unauthorized access even if one of the factors is compromised.
When is SCA Required?
SCA must be applied in the following cases:
- Accessing account information
- Initiating electronic payments
- Any action that may imply a risk of payment fraud or abuse However, several exemptions are allowed under certain risk and transaction conditions, which can help improve user experience by avoiding unnecessary friction in low-risk scenarios.
SCA Exemptions
While Strong Customer Authentication (SCA) is required for most electronic payments, PSD2 defines several exemptions that allow transactions to be processed without triggering customer authentication. These exemptions are intended to reduce friction and optimize user experience when the associated fraud risk is considered low.
Possible values for field sca_exemption
| values | description |
|---|---|
| LVV | Low Value |
| TRA | Transaction Risk Analysis |
| COR | Corporate Pay |
| MIT | Merchant Initiated Transactions |
| ATD | Additional Transaction Data |
Low-Risk Transactions (TRA – Transaction Risk Analysis)
Transactions may be exempt from SCA if both the Payment Service Provider (PSP) and the issuer meet the required fraud rate thresholds and have real-time risk analysis mechanisms in place.
| Fraud Rate Threshold | Maximum Transaction Amount |
|---|---|
| ≤ 0.13% | up to €100 |
| ≤ 0.06% | up to €250 |
| ≤ 0.01% | up to €500 |
If either the PSP or the issuer exceeds these fraud rates, the exemption may be rejected, and the transaction will require SCA.
Low-Value Payments (LWV)
- SCA is required after 5 consecutive uses of this exemption without authentication, or
- If the cumulative amount of exempted transactions exceeds €100 These limits are tracked by the issuer, who may choose to prompt for SCA even within those thresholds. In most cases, the TRA exemption is preferred over LWV due to its greater flexibility.
Recurring Transactions and Subscriptions
Recurring payments of fixed amount and frequency are only subject to SCA on the first transaction. Subsequent charges are exempt, provided they match the original terms and were initiated with customer consent.
Trusted Beneficiaries
Customers may add specific merchants to a trusted list maintained by their bank. Transactions from trusted beneficiaries can be exempted from SCA automatically, subject to issuer support and customer opt-in.
MIT – Merchant-Initiated Transactions
Merchant-Initiated Transactions (MITs), such as those using stored credentials or references, occur without the cardholder present. These are technically out of scope for SCA, but in practice they are often treated as exemptions. Conditions:
- The initial transaction (when credentials were stored) must have been authenticated
- The customer must have agreed to future charges (known as a mandate) As with all exemptions, issuers can reject MITs and request SCA at their discretion.
Additional Exemptions
Other scenarios may be exempt from SCA under PSD2, including:
- Mail Order / Telephone Order (MO/TO: Transactions where card details are collected by phone are out of scope, but must be flagged accordingly.
- Corporate Payments: Transactions made using corporate cards through channels not accessible to consumers may be exempt, depending on issuer policy.