UK
Leveraging PSD2
Account Aggregation - AISP
Dive deeper into transactional data and create value-added services
Payment Initiation - PISP
Accept A2A payments with the Fabrick licence
Bank coverage via API
Discover all of our connected banks
Mastering end-to-end payments
Fabrick Payment Orchestra
Enhance your payment management system and your information flows
Fabrick Payment Gateway
Accept payments on your website and app
Fabrick Advice
Leveraging SCA exemptions with real-time risk analysis
Fabrick Guaranteed payments
Secure payments with post-authorisation fraud checks and chargeback guarantee
Unlocking banking services for businesses
Lending Place
Offer quick and easy loans
Industry
Banking and Financial Services
Fashion
Fintech
Ho.Re.Ca.
Insurance
Customer stories
Insights
Articles
Whitepapers
Developers
Our APIs
Fabrick Producers
TPP Portal
Login Consumer Portal Fabrick
Corporate
Fabrick ecosystem
Our history
Our mission
Management Team
The Open Finance platform
Fabrick People
Our team
Why Fabrick
Career opportunities
Media Hub
Press releases
Press review
Events
Media kit
SupportBanking as a ServiceWhy does a payment result in a CORE type while the client is a FINANCIAN type?

Why does a payment result in a CORE type while the client is a FINANCIAN type?

A payment results in a CORE type while the client is a FINANCIAN type because the types below are logical subcategorizations of CORE type payments:

  • STANDARD
  • FINANCIAN
  • FIXED_AMOUNT

Do you need assistance on
Banking as a Service?

Ask for support