Fidel API provides a developer-friendly, secure and reliable API for businesses to link payment cards with mobile and web applications. Through a single API, developers can securely access data from the three major card networks and build their applications on top of the powerful payments infrastructure.
When a consumer makes a purchase at a participating store with a linked card, Fidel API spots that transaction and sends it to your server in real-time through webhooks. 💳⚡️
Fidel API runs on top of global payment networks, so it doesn’t require changes to existing merchant infrastructures. No need for new software, POS integrations, staff training or new cards. All the PCI compliance requirements are managed by us so you don’t have to.
Currently, the API is available in the United States, UK, Ireland and Canada, while Sweden, Norway and Finland are in the beta stage. Australia, New Zealand, Japan and Singapore are also on our radar. Read the full list of available locations for the Select Transactions API and for the Transaction Stream API on the product pages. We work continuously to add support for other countries and networks. If you would like to deploy card-linked applications in other countries please contact us at firstname.lastname@example.org.
You can see an example implementation for integrating the Fidel APIs and Web SDK in our sample application on GitHub.
Check out the API Reference to see all available requests, code examples and response payloads.
Join our Developer Community for API discussions, documentation, frequently asked questions, roadmap and new features. We’re always happy to help and answer any questions.
By using Fidel SDKs, card details are sent directly to Fidel API through a secure connection without exposing your servers to sensitive information taking care of all PCI compliance requirements. Our Card-Linking tutorial explains in detail all the steps required to build a card-linking feature into your application using the Fidel SDKs.
Your apps will receive an
id back that identifies the card in each transaction.
Use one of our test card numbers (for example
4444000000004004) and enter an expiry date in the future.
Web SDK integration script
Check the Web SDK documentation section for more information about all available parameters, customization options, and the metadata nested object.