HPP APM Methods
All APM payment methods supported by the Hosted Payment Page, with identifiers, action types, and currency constraints.
The Hosted Payment Page (HPP) supports the following APM methods. Each method is passed as the paymentMethod value inside apmPayload when creating a Payment Intent via POST /api/v1/payments/intent.
The HPP handles all provider interaction, redirects, and customer UI — no method-specific logic is required on your server.
All HPP APM methods return actionType: REDIRECTION in the initial response, except QR-based methods which return actionType: QR. Always use the webhook callback as the source of truth for final payment status.
#Redirection Methods
The HPP redirects the customer to the provider's hosted page. After the customer completes payment, Exirom posts the result to your callbackUrl.
| Method | Identifier | Payment Type | Currency | iFrame supported |
|---|---|---|---|---|
| Apple Pay | EXTERNAL_HPP_APPLE_PAY | E_WALLET | Merchant config | No |
| Google Pay | EXTERNAL_HPP_GOOGLE_PAY | E_WALLET | Merchant config | No |
| BLIK | EXTERNAL_HPP_BLIK | BANK_TRANSFER | PLN | No |
| EFT (Instant) | EXTERNAL_HPP_EFT | BANK_TRANSFER | Merchant config | Yes (provider-dependent) |
#Apple Pay
EXTERNAL_HPP_APPLE_PAY — The HPP collects the Apple Pay token and handles the provider interaction. No Apple Pay session management or device data is required on your server.
#Google Pay
EXTERNAL_HPP_GOOGLE_PAY — The HPP collects the Google Pay token. No native Google Pay SDK integration required on your side.
#BLIK
EXTERNAL_HPP_BLIK — The HPP handles BLIK code entry and bank app confirmation. BLIK does not support iframe embedding — always redirect to redirectUrl.
#EFT
EXTERNAL_HPP_EFT — Instant EFT bank transfer. Currency and country availability depends on your merchant agreement with the provider.
#QR Methods
The HPP generates a QR code for the customer to scan. actionType is QR. Render apmResponseData.qrData (Base64 PNG) as an image; on mobile, open qrDeepLink to launch the customer's app directly.
QR codes expire in 1–5 minutes. Show a countdown timer and offer a "Refresh QR" option on expiry.
| Method | Identifier | Payment Type | Currency | Deep link |
|---|---|---|---|---|
| PIX QR | PIX_QR | E_WALLET | BRL only | Yes |
| UPI QR | UPI_QR | BANK_TRANSFER | INR only | Yes |
| AstroPay QR | ASTRO_PAY_QR | E_WALLET | Merchant config | May be null |
#PIX QR
PIX_QR — Brazil's instant payment network. Customers scan the QR code using any Pix-enabled banking or payment app. qrDeepLink is always populated.
#UPI QR
UPI_QR — India's Unified Payments Interface. Customers scan using any UPI-enabled app. qrDeepLink is always populated.
#AstroPay QR
ASTRO_PAY_QR — AstroPay wallet via QR code. Customers scan using the AstroPay mobile app. qrDeepLink may be null for this method.
#See Also
- POST /api/v1/payments/intent — Create a Payment Intent for HPP
- HPP Flow — End-to-end HPP integration flow
- Processing the Payment Response — How to handle
REDIRECTIONandQRaction types - APM Payload References — Full
apmPayloadfield reference