1. Reference
Partner API
  • Getting Started
    • Introduction
    • Authentication
    • Business Use Cases
  • API References
    • Balances & History
      • Get Balances
      • Get Balance History
    • Crypto Deposits
      • Get Crypto Deposit Details
      • Update Travel Rule
    • Crypto Withdrawals
      • Add Whitelisted Wallet
      • Get Whitelisted Wallets
      • Delete Whitelisted Wallet
      • Create Crypto Withdrawal
      • Get Crypto Withdrawal Details
    • SEPA Deposits
      • Get SEPA Payment Details
      • Get SEPA Deposit Details
    • SEPA Withdrawals
      • Create SEPA Withdrawal
      • Get SEPA Withdrawal Details
    • Currency Exchange
      • Get Rates
      • Create Lock
      • Create Exchange
      • Get Exchange Details
  • Integration
    • Integration Guides
    • Transaction Processing
    • Error Handling
    • Rate Limiting
    • Webhooks
      • Crypto Deposit Webhook
      • Crypto Withdrawal Webhook
      • SEPA Deposit Webhook
      • SEPA Withdrawal Webhook
      • Exchange Webhook
  • Reference
    • Supported Currencies
    • Fees
    • FAQ
    • Changelog
    • Support
  1. Reference

FAQ

Quick answers to common questions about using the Fintegence Partner API.
This page focuses on the most common onboarding, authentication, KYC, payments, and webhook questions that appear during integration.

General and Authentication#

How do I get API credentials?
To access the Fintegence Partner API, you need to complete the partner onboarding process.
1.
Contact support@fintegence.com and request partner onboarding.
2.
Our team reviews your setup and onboarding details.
3.
After approval, your Business Account is prepared.
4.
You receive:
a staging API key,
a production API key,
a webhook security token.
What is the difference between staging and production?
EnvironmentBase URLPurposeData
Staginghttps://stage-api.fintegence.ioDevelopment and testingTest data
Productionhttps://api.fintegence.ioLive operationsReal funds and transactions
Best practices:
always validate full flows in staging first,
never mix staging keys with production URLs,
keep environment switching configurable in your backend.
Why am I getting 401 Unauthorized?
This usually means there is an API key or environment mismatch.
Check the following:
the request includes the x-api-key header,
the key has no leading or trailing spaces,
the key belongs to the same environment as the URL,
in production, your server IP is whitelisted.
Typical causes:
xo1: API key not provided,
xo2: API key invalid,
xo3: production request comes from a non-whitelisted IP.
Does a 2xx response mean the transaction succeeded?
No. In the Fintegence API, a 2xx response usually means the request was accepted into the processing queue.
The final outcome is determined later during background processing, for example after balance checks, compliance validation, or risk review. Always confirm the final state through:
the relevant webhook, or
the matching details endpoint.

Exchange, Payments, and Travel Rule#

What is the difference between Get Rates and Create a Lock?
Get Rates is informational. It gives you an indicative market price.
Create a Lock gives you an executable rate that is reserved for a short time window, approximately 60 seconds in the current documented exchange flow.
Typical pattern:
1.
show an estimate with Get Rates,
2.
request a final executable quote with Create a Lock,
3.
use the returned lockId immediately for execution.
What is the difference between Standard Payment Link and Hosted Checkout?
Standard Payment Link uses the global Fintegence standard configuration.
Hosted Checkout uses your dedicated partner configuration and brand identity.
In practice:
Standard Payment Link is the faster standard setup,
Hosted Checkout is the more tailored white-label setup,
Hosted Checkout requires onboarding-time configuration for things such as branding, lock durations, and underpayment windows.
What is the Travel Rule and when do I need to act?
Travel Rule handling becomes relevant when a crypto deposit enters WAITING_FOR_TR_DATA.
At that point:
the deposit remains locked,
you must submit the required originator data,
compliance review must pass before the funds are released.
Use the crypto deposit webhook to detect the status transition and use the Update Travel Rule endpoint to provide the required sender details.
How should I think about fees?
Treat fees as a commercial layer defined by your agreement with Fintegence.
At a high level:
pricing may apply across exchanges, SEPA withdrawals, crypto withdrawals, KYC-related services, and other enabled product operations,
internal transfers are the current fee-free exception,
for crypto withdrawals, the operational cost view may include both configured withdrawal fee data from balances and the current dynamic network fee.
For implementation guidance, use the dedicated Fees page rather than hardcoding assumptions from examples.

Webhooks and Operational Reliability#

How do I verify webhook authenticity?
Every webhook request includes your shared secret in the Authorization header.
Recommended process:
1.
read the Authorization header,
2.
compare it with your stored webhook secret,
3.
return 401 for missing or invalid values,
4.
only process payloads that pass verification.
What happens if my webhook endpoint fails?
Webhook delivery is retried automatically when your endpoint fails or does not acknowledge the request correctly.
Current documented retry model:
AttemptDelay After Previous Failure
1stInitial delivery
2nd~8 seconds
3rd~16 seconds
4th~32 seconds
5th~64 seconds
Retry is triggered by non-2xx responses or timeouts. Each request times out after approximately 10 seconds.
Your webhook consumer should be idempotent, because the same event may be delivered more than once.
Are card services currently available?
Current documentation marks card services and card webhooks as suspended.
If your commercial agreement mentions card-related capabilities, treat them as inactive unless Fintegence explicitly re-enables that module for your environment.
Previous
Fees
Next
Changelog
Built with