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
Fabrick Payment Facilitator
Get pre-reconciled credits directly into your account
Unlocking banking services for businesses
Lending Place
Offer quick and easy loans
Fabrick Smart Banking
Create a customised app where digital payment services can be integrated
Industry
Banking and Financial Services
Fashion
Fintech
Ho.Re.Ca.
Insurance
Automotive
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
SupportPSD2 ServicesWhat should FPP or TPP do during the development phase before moving on to the production environment?

What should FPP or TPP do during the development phase before moving on to the production environment?

Type: AISP
Product: PSD2 Active Engine

When an FPP or TPP switches to the production environment, it must verify the following elements:

  • Modify apiKey (available from the Consumer Portal in the appropriate section) and domain (available in the API documentation)
  • FPP only: verify that all required customisations are correct (e.g. text logo configurations)

Do you need assistance on
PSD2 Services?

Ask for support