HyperPay · FinOps Profile

Hyperpay Finops

FinOps view of HyperPay merchant costs. Unlike usage-metered API vendors, HyperPay's cost model is payment-processing economics: a fixed setup fee, a recurring monthly gateway fee, and per-transaction fees that vary by payment method (cards vs. the domestic mada scheme), plus separate acquiring-bank fees. Costs scale with transaction count and volume (GMV) and settle in SAR.

Hyperpay Finops is the FinOps profile for HyperPay on the APIs.io network, aligned with the FinOps Foundation Framework.

It defines 5 billable meters, billed in SAR, on a monthly cycle, and pricing category transaction-based.

The profile maps 8 FOCUS columns for cost-allocation reporting.

Tagged areas include Payments, Payment Gateway, MENA, Saudi Arabia, and FinOps.

Category: Payment Processing Pricing: Transaction-Based Billing: Monthly FOCUS v1.3
PaymentsPayment GatewayMENASaudi ArabiaFinOpsCost ManagementFOCUS

Framework Alignment

Framework
FinOps Foundation Framework
Data Spec
FOCUS v1.3

Charge Categories

UsagePurchase

FOCUS Columns

BillingCurrency
SAR
ChargeCategory
Usage
InvoiceIssuerName
HyperPay
PricingCategory
Transaction-Based
ProviderName
HyperPay
PublisherName
HyperPay
ServiceCategory
Payment Processing
ServiceName
HyperPay Payment Gateway

Meters

setup_fee
Unit: account
One-time onboarding / setup fee charged when the merchant channel is provisioned.
monthly_gateway_fee
Unit: months
Recurring monthly gateway subscription fee.
card_transaction_fee
Unit: transactions
Percentage-plus-fixed fee per card transaction (VISA / MASTER / AMEX).
mada_transaction_fee
Unit: transactions
Percentage-plus-fixed fee per mada domestic-scheme transaction (typically lower than cards).
refund_chargeback_fees
Unit: events
Fees associated with refunds, chargebacks, and reversals via the back-office API.

Sources