Card management

​

Introduction to Card Management API

Implementing our API for card management, provides significant advantages. It allows businesses to automate and streamline their card-related operations, enhancing efficiency, security, and user experience. This can be particularly beneficial for companies with multiple employees needing access to company funds or for those who prioritize tight financial control and security.

​

Advantages of Qonto’s Card API

1. Automation: Automates card issuance, activation, and management processes, reducing manual workload.
2. Security: Provides robust security features like locking/unlocking cards and reporting lost/stolen cards, ensuring financial safety.
3. Control: Allows setting limits and restrictions on cards, offering detailed control over expenditures.
4. Flexibility: Supports both physical and virtual cards, catering to diverse business needs.
5. Integration: Seamless integration with existing financial tools and systems through OAuth 2.0.

​

Use Cases and Technical Implementation

​

1. Create Cards

• Endpoint: /v2/cards
  • Use Case: Automate the issuance of new cards for employees.
  • Requirements: Ensure all required fields such as type, holder, and initial limits are correctly filled. As creating a card is a sensitive this endpoint requires SCA.

​

1.1 Create cards in bulk

• Endpoint: /v2/cards/bulk
  • Use Case: Automate card issuance for teams and departments.
  • Requirements: Ensure all required fields such as type, holder, and initial limits are correctly filled.

​

2. List Cards

• Endpoint: /v2/cards
• Use Case: Retrieve a list of all cards under an organization for auditing or management purposes.

​

3. Retrieve a Card iFrame URL

• Endpoint: /v2/cards//data_view
• Use Case: Securely display card details or management options within an application. Use the GET method to retrieve a URL that can be embedded securely within your application.

​

4. Manage Your Card Lifecycle

Report a Card as Lost or Stolen

• Endpoints:
  • /v2/cards//lost
  • /v2/cards//stolen
• Use Case: Immediately deactivate cards that are lost or stolen to prevent unauthorized transactions.

Discard a Virtual Card

• Endpoint: /v2/cards//discard
• Use Case: Permanently deactivate unused or compromised virtual cards.

Lock and Unlock a Card

• Endpoints:
  • /v2/cards//lock
  • /v2/cards//unlock
• Use Case: Temporarily disable cards during suspicious activity or when not in use. Unlocking a card is a sensitive this endpoint requires SCA.

​

5. Change Card Settings

Update Card Limits and Restrictions

• Endpoints:
  • /v2/cards//limits for updating spending limits. SCA is required for this endpoint.
  • /v2/cards//restrictions for setting usage restrictions such as geographical or vendor-specific limits.
• Use Case: Manage and adjust spending policies dynamically to align with business needs.

Update Card Options and Nickname

• Endpoints:
  • /v2/cards//options for general card settings.
  • /v2/cards//nickname to personalize card identification.
• Use Case: Customize card settings to enhance usability and identification within the organization.

​

What does it look like?