Start here
/
Getting started

Getting started

Use the FINCI Card API to create customer and account records, issue cards and manage their lifecycle. Receive webhooks to handle authorization decisions, outcome confirmations and clearing records.

API access is provided through an approved FINCI card program. In these guides, integrator means your organization and the backend you build to connect to FINCI.

Confirm your services and responsibilities in Program models. Physical cards, wallets, 3D Secure and Payments API reconciliation apply when included in your program. Use Definitions for unfamiliar terms.

Integration surfaces

  • Card API: Your backend sends REST requests to FINCI for customer and account setup, card issuance and card management.
  • Webhooks: FINCI sends authorization requests, outcomes and presentments to your registered backend endpoints.

Build the integration

  1. Configure API authentication and register your webhook receivers with FINCI.
  2. Create customer, account and card records using Core data model and Issuing cards.
  3. Implement the authorization receiver: handle outcomes and related updates. If your program uses integrator-managed decisions, approve or decline within 3 seconds.
  4. Implement the presentment receiver: post each local account movement once and release the full matching hold.
  5. Validate the transaction use cases with the Integration test plan, then complete validation and go-live.

The rules come first in each guide. Use the diagrams and complete messages to check your implementation against the same flow.

System overview

Your backend connects to FINCI in two directions. Select one to see its purpose.

Your backend sends Card API requests to FINCI to create and manage customers, accounts and cards. FINCI sends webhooks to your backend for authorization decisions, confirmations and presentments.

For a payment walkthrough and complete webhook messages, open Transaction lifecycle. For record relationships, open Core data model.

Implementation journey

  1. Agree the program model, services and responsibilities. Start FINCI onboarding and complete the compliance review.
  2. Receive sandbox access and authentication materials. Complete sandbox IP whitelisting and register your webhook endpoints.
  3. Build the setup, card and transaction handlers described above. Confirm program-specific settings with FINCI integration support.
  4. Complete sandbox validation and review the test evidence with FINCI.
  5. Submit the signed production access confirmation document and production IP whitelist details. Obtain production approval and live access.
  6. Complete production confirmation testing, operational readiness and the final go-live review before launch.

Synchronous versus asynchronous work

InterfaceHow your backend handles it
Card API
Send a signed REST request and process the response.
Initial authorization webhook
In integrator-managed programs, approve with HTTP 200 + {"status":"success"} or decline with HTTP 403 + {"status":"error"} within 3 seconds.
Outcome confirmation and presentment
Receive and store the event durably. Apply each state change or posting once, including retries.

Start with the purchase example, then use Transaction use cases to add declines, amount changes, reversals, refunds and matching exceptions.

Built with