APIs · head to head
AWS API Gateway vs Enfuce

AWS API Gateway
APIs
Fully managed API gateway service for creating and managing APIs at scale
- From
- Free
- Rated
- -

Enfuce
APIs
European issuer processor holding its own payment institution licence
- From
- On request
- Rated
- -
The short version
- Only AWS API Gateway has a free tier, so it costs nothing to try first.
- Each has a real cost: AWS API Gateway rEST APIs cost $3.50 per million calls against $1.00 for HTTP APIs, so the older and more featureful type is three and a half times dearer; Enfuce coverage is European, so a programme that also needs US or Asian issuing requires a separate processor and a separate integration.
- They diverge on capability: AWS API Gateway covers REST APIs, Enfuce covers Licensed issuing.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which AWS API Gateway and Enfuce actually diverge.
| Attribute | AWS API Gateway | Enfuce |
|---|---|---|
| Starting price | Free | On request |
| Pricing model | usage-based | quote |
| Free tier | Yes | No |
| Platforms | AWS Cloud | Web, REST API |
| Founded | 2006 | Unknown |
Identical on both: user rating (Not yet rated), category (APIs).
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in AWS API Gateway
- REST APIs
- WebSocket APIs
- HTTP APIs
- Lambda
- EC2
- DynamoDB
- CloudWatch
- IAM
Only in Enfuce
- Licensed issuing
- Card processing
- Tokenisation
- Spend controls
- Multi-currency programmes
- Carbon and data services
What people use each for
The jobs each tool is most often brought in to do.
AWS API Gateway
- Fronting Lambda functions with an HTTP endpointnot Enfuce
- REST and HTTP API management with throttling and keysnot Enfuce
- WebSocket APIs for real-time clientsnot Enfuce
- Private APIs reachable only inside a VPCnot Enfuce
- Publishing a developer portal for API consumersnot Enfuce
Enfuce
- A European fintech launching cards without spending two quarters finding a sponsor banknot AWS API Gateway
- A corporate issuing fuel or expense cards across several EU countries on one programmenot AWS API Gateway
- A bank migrating an existing European card portfolio off a legacy processornot AWS API Gateway
- A programme that must report cardholder transaction carbon data to meet sustainability commitmentsnot AWS API Gateway
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
AWS API Gateway
- REST APIs cost $3.50 per million calls against $1.00 for HTTP APIs, so the older and more featureful type is three and a half times dearer
- Data transfer out is charged at $0.09 per GB on top of request pricing
- WebSocket APIs bill connection minutes as well as messages, at $0.25 per million minutes
- Private APIs avoid data transfer charges but incur AWS PrivateLink costs instead
- The developer portal is $125 a month, with additional portal products at $12.50 each
- The free tier lasts 12 months rather than being ongoing
Enfuce
- Coverage is European, so a programme that also needs US or Asian issuing requires a separate processor and a separate integration.
- Where Enfuce acts as the licensed issuer it takes on regulatory risk and prices accordingly, so the convenience of skipping a sponsor bank is not free.
- European interchange caps limit programme revenue far below US levels, so business cases imported from a US card model do not survive the move.
- It is a smaller supplier than Marqeta or i2c, which means less negotiating room on scheme fees and a thinner partner ecosystem around it.
- Pricing is entirely quoted with monthly minimums, so low-volume programmes carry a fixed cost that does not scale down with a slow launch.
Pricing, plan by plan
AWS API Gateway
Free- Free Tier (12 months)Free
- 1M REST API calls per month
- 1M HTTP API calls per month
- 1M WebSocket messages plus 750K connection minutes per month
- HTTP APIs$1/per million requests (first 300M)
- First 300M: $1.00 per million
- Next 132M: $0.90 per million
- Data transfer varies by volume
- REST APIs$3.5/per million API calls
- Edge Optimized and Regional: $3.50 per million (first tier)
- Higher volumes: $2.80 then $2.38 per million
- Data transfer: $0.09 per GB
- WebSocket APIs$1/per million messages
- Messages: $1.00 per million
- Connection minutes: $0.25 per million minutes
Enfuce
On request- Enfuce issuing and processing$undefined/year
- Per-active-card and per-transaction fees with monthly minimums
- Higher pricing where Enfuce acts as licensed issuer rather than processor only
- Interchange arrangements depend on who holds the issuing licence
Which should you pick?
Choose AWS API Gateway if
- You need rest apis.
- You want to start without paying.
- You work on AWS Cloud.
- You also want websocket apis.
Choose Enfuce if
- You need licensed issuing.
- You work on Web, REST API.
- You also want card processing.
Questions people ask
- Is AWS API Gateway or Enfuce better?
- Neither clearly leads. AWS API Gateway starts at Free and Enfuce at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, AWS API Gateway or Enfuce?
- AWS API Gateway has a free tier; the other does not. Paid plans start at Free for AWS API Gateway and On request for Enfuce.
- Does AWS API Gateway or Enfuce run on more platforms?
- AWS API Gateway runs on AWS Cloud. Enfuce runs on Web, REST API.
- Can I use AWS API Gateway for free?
- Yes. AWS API Gateway has a free tier, so you can try it without paying. Enfuce starts at On request.
- What is AWS API Gateway best used for?
- AWS API Gateway is most often used for fronting lambda functions with an http endpoint, rest and http api management with throttling and keys, websocket apis for real-time clients, private apis reachable only inside a vpc. Of those, fronting lambda functions with an http endpoint and rest and http api management with throttling and keys are not what Enfuce is typically brought in for.
- What can AWS API Gateway do that Enfuce cannot?
- AWS API Gateway covers REST APIs, WebSocket APIs, HTTP APIs, Lambda. Enfuce covers Licensed issuing, Card processing, Tokenisation, Spend controls.
Answered from the vendors’ own pages
AWS API Gateway: How much does AWS API Gateway cost?
AWS API Gateway pricing varies by API type. HTTP APIs cost $1.00 per million requests for the first 300M monthly, then $0.90 per million. REST APIs cost $3.50 per million, and WebSocket APIs cost $1.00 per million messages plus $0.25 per million connection minutes. Data transfer charges ($0.09 per GB) apply separately.
SourceEnfuce: Do I need my own licence to use Enfuce?
Not necessarily. Enfuce holds Finnish payment institution authorisation and can act as issuer, or process under your own licence if you have one.
AWS API Gateway: Is AWS API Gateway free?
New AWS customers receive 12 months of free tier access including 1 million REST API calls, 1 million HTTP API calls, and 1 million WebSocket messages plus 750,000 connection minutes per month. Starting July 15, 2025, new customers receive up to $200 in AWS Free Tier credits.
SourceEnfuce: Which regions does it cover?
Europe. It is not a route to issuing cards in the United States or Asia.
AWS API Gateway: What is the price difference between HTTP and REST APIs?
HTTP APIs are significantly cheaper at $1.00 per million requests compared to REST APIs at $3.50 per million (first tier). REST API pricing decreases to $2.80 and $2.38 per million for higher volumes, while HTTP API pricing drops to $0.90 per million after 300M monthly requests.
SourceEnfuce: How does interchange work?
Who holds the issuing licence determines who receives interchange, so the licensing choice and the revenue model are the same decision.
AWS API Gateway: How much does an API Gateway Portal cost?
API Gateway Portals require a base fee of $125 per month (includes 10 PortalProducts with 40 endpoints each) plus $12.50 per month for each additional PortalProduct beyond the included 10.
SourceRelated pages
More on AWS API Gateway
Other head to heads
- AWS API Gateway vs Appwrite
- AWS API Gateway vs Hasura
- AWS API Gateway vs PocketBase
- AWS API Gateway vs Sanity
- AWS API Gateway vs Microsoft Azure API Management
- AWS API Gateway vs Kong
- AWS API Gateway vs Convoy
- AWS API Gateway vs Tyk
- AWS API Gateway vs Janus Gateway
- AWS API Gateway vs Spring Cloud Gateway
- AWS API Gateway vs Gravitee
- AWS API Gateway vs REST Client VSCode
- AWS API Gateway vs Rutter
- AWS API Gateway vs Sensedia
- AWS API Gateway vs Sila
- AWS API Gateway vs Swagger
- AWS API Gateway vs Kong Gateway
- AWS API Gateway vs Marqeta
- AWS API Gateway vs i2c
- AWS API Gateway vs Weavr
- AWS API Gateway vs Tink
- AWS API Gateway vs Paymentology
- AWS API Gateway vs Highnote
- AWS API Gateway vs Lithic
- AWS API Gateway vs Thredd
- AWS API Gateway vs Episode Six
- AWS API Gateway vs Tribe Payments
- AWS API Gateway vs Enable Banking
- AWS API Gateway vs Salt Edge
- AWS API Gateway vs Skyflow
- AWS API Gateway vs Yodlee
- AWS API Gateway vs Backbase
- AWS API Gateway vs Griffin
- AWS API Gateway vs Stoplight
- Enfuce vs Appwrite
- Enfuce vs Hasura
- Enfuce vs PocketBase
- Enfuce vs Sanity
- Enfuce vs Microsoft Azure API Management
- Enfuce vs Kong
- Enfuce vs Convoy
- Enfuce vs Tyk
- Enfuce vs Janus Gateway
- Enfuce vs Spring Cloud Gateway
- Enfuce vs Gravitee
- Enfuce vs REST Client VSCode
- Enfuce vs Rutter
- Enfuce vs Sensedia
- Enfuce vs Sila
- Enfuce vs Swagger
- Enfuce vs Kong Gateway
- Enfuce vs Marqeta
- Enfuce vs i2c
- Enfuce vs Weavr
- Enfuce vs Tink
- Enfuce vs Paymentology
- Enfuce vs Highnote
- Enfuce vs Lithic
- Enfuce vs Thredd
- Enfuce vs Episode Six
- Enfuce vs Tribe Payments
- Enfuce vs Enable Banking
- Enfuce vs Salt Edge
- Enfuce vs Skyflow
- Enfuce vs Yodlee
- Enfuce vs Backbase
- Enfuce vs Griffin
- Enfuce vs Stoplight
