The G2A Pay Payment Gateway module supports the following currencies: GBP, USD, EUR, PLN, and AUD. These five ISO codes are the only ones the module processes natively. Merchants must configure their store to use one of these currencies as the base or active transaction currency to ensure reliable payment processing.

Currency compatibility directly affects checkout success rates and operational costs. When a customer's billing currency matches a supported option, conversion fees are minimized and the transaction risk profile improves. On Windows/.NET hosting environments, the payment module reads the cart currency and submits it to the G2A endpoint; a mismatch can trigger immediate declines or require custom handling in your order pipeline. Confirming support early prevents downstream errors in tax calculation, pricing display, and reconciliation.

#Supported Currencies

  • GBP - British Pound Sterling, the primary currency of the United Kingdom and a benchmark for many international transactions.
  • USD - United States Dollar, the most widely accepted currency for global digital commerce and cross-border sales.
  • EUR - Euro, serving the Eurozone and simplifying payments for customers across much of continental Europe.
  • PLN - Polish Zloty, the national currency of Poland and a key market for G2A's core customer base.
  • AUD - Australian Dollar, used throughout Australia and relevant for Oceania-based buyers.

#Integration Considerations for .NET Applications

When integrating the G2A Pay module into an ASP.NET or ASP.NET Core shopping cart, set the store's default currency to one of the five supported values before enabling the gateway. The module expects the currency code to be passed in the standard three-letter ISO format. Perform this configuration in the admin panel under payment methods, then update any regional pricing tables to match. After saving changes, clear application caches and restart the application pool to ensure the new settings are loaded. Test with small orders in sandbox mode using each currency to confirm the API accepts the payload and returns successful responses. This validation step surfaces configuration problems before they reach production traffic.

csharp 
public bool IsValidG2ACurrency(string currencyCode)
{
    if (string.IsNullOrEmpty(currencyCode)) return false;
    var supportedCurrencies = new[] { "GBP", "USD", "EUR", "PLN", "AUD" };
    return supportedCurrencies.Contains(currencyCode.Trim().ToUpperInvariant());
}

// Example usage in checkout handler
if (!IsValidG2ACurrency(cart.CurrencyCode))
{
    ModelState.AddModelError("Currency", "Selected currency is not supported by G2A Pay.");
    return View("CheckoutError");
}

// Proceed with G2A payment request

#Common Pitfalls

The most frequent error is enabling additional store currencies such as CAD, JPY, or CHF without realizing the module will reject them at runtime. This produces vague decline messages that are difficult to debug. Another issue occurs when the G2A merchant account is registered in one currency while the cart operates in another, causing a mismatch at the API level. Currency symbols displayed on the site are separate from the actual ISO code sent to the gateway; ensure both are aligned. Logs should be monitored for any entries containing "currency not supported" or similar strings. Finally, pricing that ends in uncommon fractional amounts can trigger rounding problems in certain currencies, so test end-to-end with realistic order totals.

#Next Steps and Resources

Begin by auditing your current store currency settings against the list above. Update pricing and test transactions in the G2A sandbox using each supported currency. Once verified, enable live processing and monitor the first few days of orders for any anomalies. For the latest details or possible expansions to the supported list, review G2A Pay's official support article here: https://pay.g2a.com/supporthub/?category=1&subcategory=54&question=19. Keep the currency validation logic in your codebase so future updates remain consistent with the gateway constraints. This disciplined approach results in fewer failed checkouts and simpler financial reconciliation.