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 ServicesIs the ‘id’ parameter that identifies each transaction unique in the GET API getPFMTransactions?

Is the ‘id’ parameter that identifies each transaction unique in the GET API getPFMTransactions?

Type: AISP
Product: PSD2 Active Engine

Yes, the ‘id’ parameter that identifies each transaction is unique in the getPFMTransactions GET API , but it could be updated if the resyncType value is CREATED_TEMPORARY.

Behaviour of the resyncType parameter:

You can find out more about the behaviour of the resyncType parameter in the documentation provided during the integration phase.

Do you need assistance on
PSD2 Services?

Ask for support