Enfuce

"Payment Processing & Card Issuing Platform for Growth" [1]

enfuce.com · By Enfuce · Agent JSON · Suggest an edit · Last verified 2026-06-21 · Source confidence: high

Enfuce is a card issuing and payment processing platform for fintechs, brands, and enterprises looking to launch debit, prepaid, credit, or specialty card programs (expense, fleet, EV, kids) without needing their own EMI license or scheme membership, as Enfuce holds dual EMI authorization from the Finnish FSA and UK FCA and is a principal Visa and Mastercard member. It covers the full card lifecycle via REST APIs, including spend controls, tokenization, 3DS, dispute management, KYC/KYB, and real-time webhooks, with a sandbox available for self-serve testing. Geographic coverage spans the EEA, United Kingdom, and Latin America, and the platform is PCI DSS Level 1 certified. Pricing is quote-only with no published rates.

Best for / Avoid if

Best for: AI agents and automation - an agent-ready surface (MCP / llms.txt); Teams needing broad API coverage out of the box

Avoid if: You need transparent pricing up front; You want to try it free before paying; You have strict compliance requirements

Pricing & procurement

Pricing model
Contact sales [2]
Published pricing
No [3]
Free tier
No
Self-serve signup
Yes [4]
Requires sales call
Yes [5]
Enterprise plan
Unknown

Capabilities

  • Virtual cards
  • Physical cards
  • Spend controls
  • BIN sponsorship
  • Credit programs
  • Push provisioning
  • Multi-region
Supported actions
issue_virtual_card, issue_physical_card, spend_controls, authorization_stream, card_lifecycle_management, program_management, tokenization, 3ds, dispute_management, fraud_monitoring, kyc_kyb, real_time_webhooks, digital_wallet_provisioning, multi_currency_support, jit_funding_flexible_balance, bin_sponsorship, settlement, authorization_forwarding, invoice_management, instalment_credit, revolving_credit, data_export [6]
Regions
EEA, United Kingdom, Brazil (Latin America) [7]
Input types
Visa, Mastercard, virtual, physical, debit, credit, prepaid, dual-PAN, fuel, consumer, commercial [8]
Output types
JSON, webhook events, card tokens, authorization events, transaction data, statements, data export files, invoice data [9]
Webhooks
Yes [10]
Sandbox / test mode
Yes [11]
SDK languages
Unknown
MCP server
No

Trust & compliance

SOC 2
Unknown [12]
HIPAA
No [13]
GDPR
Yes [14]
ISO 27001
Unknown [15]
PCI DSS
Yes [16]
Published SLA
No [17]
Rate limits
Sandbox environment: 5 requests per second / 1,000 requests per day (per Enfuce developer portal documentation) [18]
Known restrictions
Enfuce provides turnkey BIN sponsorship - clients do NOT need their own sponsor bank or EMI license (Enfuce is a dual-regulated EMI authorized by Finnish FSA and UK FCA), Enfuce is a principal member of Visa and Mastercard - scheme membership is included in the BIN sponsorship service, PCI DSS Level 1 certified (assessed annually); clients are kept out of PCI scope; Enfuce was the first financial service provider in the world to achieve PCI-DSS certification while running in the public cloud, BIN sponsorship scope: EEA and UK fully documented; Brazil/Latin America operations confirmed via Swile partnership (Nov 2025) but BIN sponsorship availability there not explicitly documented, Production card issuance requires onboarding/sales engagement; sandbox is self-serve via console.myedge.enfuce.com/signup, No published per-card or per-transaction pricing; pricing is per-card/monthly but quote-only, ISO 27001 and SOC 2 certifications not found on any official Enfuce page [19]

Developer surface

Docs rendering: static · llms.txt present

Integration

API style
rest
Base URL
https://integration-api-cat2.live.ext.prod.cia.enfuce.com
Version
v3
Versioning
url
Stability
ga
Auth methods
basic
Idempotency keys
Yes
Error format
vendor-specific

Adoption & maturity

Launched
2016-01-01
Notable customers
Pleo, Swile, Memo Bank, SEB Embedded, Qred, Octopus Electroverse, allpay, Mynt, Shuttel

Other Card Issuing APIs

  • Lithic

    "Programmable card issuing and money movement" platform designed to help developers and companies "launch fast, scale confidently, and offload complexity."

    Usage · public pricing · self-serve

  • Stripe Issuing

    "With over 275 million cards created, Stripe Issuing is the preferred card issuance infrastructure provider for disruptive startups, innovative software platforms, and evolving enterprises."

    Usage · public pricing

  • Weavr

    "Embedded finance for digital B2B products"

    Hybrid · public pricing · self-serve

  • Swan

    "The easiest way to embed banking features into your product."

    Hybrid · public pricing · self-serve

  • Wallester

    "Free business IBAN account with cards and expense management"

    Hybrid · free tier · public pricing · self-serve

  • Adyen Issuing

    "Get everything you need to create and manage your card program with our financial technology platform."

    Sales-led

Enfuce alternatives · Enfuce vs Lithic · All Card Issuing APIs APIs

References

Each field above carries a numbered source - hover for a preview, click to jump here.

  1. Description: enfuce.com
  2. Pricing model: enfuce.com · enfuce.com
  3. Published pricing: enfuce.com · enfuce.com
  4. Self-serve signup: enfuce.com · console.myedge.enfuce.com
  5. Requires sales call: enfuce.com · enfuce.com
  6. Supported actions: docs.enfuce.com
  7. Regions: enfuce.com · enfuce.com
  8. Input types: enfuce.com · enfuce.com
  9. Output types: docs.enfuce.com
  10. Webhooks: docs.enfuce.com · enfuce.com
  11. Sandbox: enfuce.com · docs.enfuce.com
  12. SOC 2: enfuce.com
  13. HIPAA: enfuce.com
  14. GDPR: enfuce.com · enfuce.com
  15. ISO 27001: enfuce.com
  16. PCI DSS: enfuce.com · enfuce.com
  17. Published SLA: enfuce.com · enfuce.com
  18. Rate limits: developer.enfuce.openbanking.enfuce.com
  19. Known restrictions: docs.enfuce.com · enfuce.com

Change history

Every field change, who made it, and when - from our audited data pipeline and editors.

  1. 2026-06-21 Capabilities: {}{"multi_region":true,"virtual_cards":true,"physical_cards":true,"spend_controls…
  2. 2026-06-21 Summary Md: (none)Enfuce is a card issuing and payment processing platform for fintechs, brands, …
  3. 2026-06-21 Score Setup Speed: (none)60
  4. 2026-06-21 Score Docs Quality: (none)45
  5. 2026-06-21 Score Procurement Friction: (none)25
  6. 2026-06-21 Score Trust Readiness: (none)25
  7. 2026-06-21 Best For: (none)AI agents and automation - an agent-ready surface (MCP / llms.txt), Teams needi…
  8. 2026-06-21 Avoid If: (none)You need transparent pricing up front, You want to try it free before paying, Y…
  9. 2026-06-21 Scoring Methodology: (none)Scores are computed deterministically from this profile's published, sourced fi…
  10. 2026-06-21 Score Agent Friendliness: (none)55
  11. 2026-06-21 Score Pricing Transparency: (none)0
  12. 2026-06-21 Llms Txt Present: (none)Yes
  13. 2026-06-21 Rendering: (none)static
  14. 2026-06-21 Has Structured Data: (none)Yes
  15. 2026-06-21 Robots Allows Agents: (none)Yes
  16. 2026-06-21 API Reference URL: (none)https://enfuce.com/wp-content/uploads/2021/04/API.png
  17. 2026-06-21 Status Page URL: (none)https://status.enfuce.com
  18. 2026-06-21 Docs URL: (none)https://docs.enfuce.com/
  19. 2026-06-21 Llms Txt URL: (none)https://enfuce.com/llms.txt
  20. 2026-06-21 Self Serve Signup: set to Yes
  21. 2026-06-21 Requires Sales Call: set to Yes
  22. 2026-06-21 HIPAA: set to No
  23. 2026-06-21 GDPR: set to Yes
  24. 2026-06-21 PCI DSS: set to Yes
  25. 2026-06-21 SLA Published: set to No
  26. 2026-06-21 Data Retention Policy URL: set to https://enfuce.com/privacy-and-data-protection/
  27. 2026-06-21 Documented Rate Limits: set to Sandbox environment: 5 requests per second / 1,000 requests per day (per Enfuce…
  28. 2026-06-21 Known Restrictions: set to Enfuce provides turnkey BIN sponsorship - clients do NOT need their own sponsor…
  29. 2026-06-21 Auth Methods: set to basic
  30. 2026-06-21 Auth Docs URL: set to https://docs.enfuce.com/payment/api/notification
  31. 2026-06-21 API Style: set to rest
  32. 2026-06-21 Base URL: set to https://integration-api-cat2.live.ext.prod.cia.enfuce.com
  33. 2026-06-21 API Version: set to v3
  34. 2026-06-21 Versioning Scheme: set to url
  35. 2026-06-21 Stability: set to ga
  36. 2026-06-21 Deprecation Policy URL: set to https://docs.enfuce.com/updates/release-notes.md
  37. 2026-06-21 Quickstart URL: set to https://docs.enfuce.com/guides/start-developing-with-enfuce
  38. 2026-06-21 Idempotency Supported: set to Yes
  39. 2026-06-21 Error Format: set to vendor-specific
  40. 2026-06-21 Webhook Events URL: set to https://docs.enfuce.com/payment/api/receive-a-notification/outgoing-webhook-not…
  41. 2026-06-21 Requires Verification: set to Yes
  42. 2026-06-21 Price Basis: set to card
  43. 2026-06-21 Slug: set to enfuce
  44. 2026-06-21 Notable Customers: set to Pleo, Swile, Memo Bank, SEB Embedded, Qred, Octopus Electroverse, allpay, Mynt,…
  45. 2026-06-21 Fields Not Found: set to iso_27001, soc2, minimum_commitment, enterprise_plan_available, sdk_languages, …
  46. 2026-06-21 Source Confidence: set to high
  47. 2026-06-21 Extractor: set to claude-subagent:sonnet
  48. 2026-06-21 Last Verified At: set to 2026-06-21T00:00:00.000Z
  49. 2026-06-21 Status: set to published
  50. 2026-06-21 Launched At: set to 2016-01-01

Suggest an edit / leave a review

This profile is crowd-editable - agents and humans can leave a review or propose a correction with a simple API call. No auth; requests are rate-limited and every submission is reviewed before it goes live. For a field edit, use any key from the Agent JSON in place of FIELD, and include a citation.

Leave a review or comment

curl -X POST https://apio.sh/api/feedback/enfuce \
  -H 'Content-Type: application/json' \
  -d '{"kind":"review","rating":5,"body":"Your experience with this API…"}'

Suggest a correction to a field (cite a source)

curl -X POST https://apio.sh/api/suggest/enfuce/FIELD \
  -H 'Content-Type: application/json' \
  -d '{"value":"corrected value","citations":[{"url":"https://source.example/page","excerpt":"supporting quote"}],"note":"what changed and why"}'

All the ways to contribute →