Midtrans Finops
FinOps view of Midtrans spend. Midtrans has no platform, setup, or monthly API fee - cost is incurred per successful transaction, priced by payment method (a percentage, a flat IDR amount, or both) and, for Iris, per payout. Because the fee is a merchant-discount-rate cut of payment volume rather than metered API usage, cost is driven by transaction mix (which methods customers choose) and gross payment value, not by call counts. Value-Added Tax applies to most methods (QRIS, GoPay, and ShopeePay are quoted VAT-inclusive).
Midtrans Finops is the FinOps profile for Midtrans on the APIs.io network, aligned with the FinOps Foundation Framework.
It defines 5 billable meters, billed in IDR, on a per-transaction cycle, and pricing category usage-based.
The profile maps 8 FOCUS columns for cost-allocation reporting.
Tagged areas include Payments, Payment Gateway, Indonesia, Fintech, and FinOps.
Framework Alignment
Charge Categories
FOCUS Columns
Meters
Sources
- https://midtrans.com/pricing
- https://docs.midtrans.com/docs/pricing
- https://docs.midtrans.com/docs/how-much-does-midtrans-charge-for-its-payment-service
- https://focus.finops.org/focus-specification/v1-3/
Work with this as data
Every finops artifact here is available over the APIs.io API and to AI agents over MCP.