This section governs all payments, account balance top-ups, payment methods, refunds, chargebacks, payment disputes, and related billing matters in connection with the FINAP Services.
1. Payment Methods
FINAP may accept payments through the following payment methods:
1. Bank cards, including Visa and Mastercard;
2. SEPA bank transfer;
3. Cryptocurrency payments, where such payment method is made available by FINAP or its payment providers;
4. Any other payment method that FINAP may introduce in the future.
Available payment methods may vary depending on the customer’s country, account status, payment amount, payment provider availability, compliance checks, sanctions screening, and risk assessment.
FINAP reserves the right to add, remove, suspend, restrict, or refuse any payment method at any time.
2. Licensed Payment Providers
Payments made to FINAP are processed by licensed, authorised, or otherwise legally permitted third-party payment providers, acquiring banks, card processors, crypto payment processors, banking partners, or other payment service providers, where applicable.
FINAP does not directly process card payments, does not acquire card transactions, does not provide payment processing services to customers, and does not act as a payment institution, electronic money institution, bank, money transmitter, cryptocurrency exchange, or custodian.
All payments are made solely for the purpose of purchasing FINAP software, API, data intelligence, validation, and technology services.
Payment processing may be subject to the terms, conditions, compliance checks, fraud screening, risk rules, sanctions screening, transaction monitoring, and technical requirements of the relevant payment provider.
3. Secure Payment Pages and 3D Secure
Card payments are processed through secure payment pages or payment forms provided by FINAP’s payment providers or acquiring partners.
Where applicable, card payments may be subject to additional authentication measures, including 3D Secure, Strong Customer Authentication, fraud screening, cardholder verification, issuer approval, or other security procedures required by the card issuer, payment processor, card scheme, acquiring bank, or applicable law.
FINAP does not collect or store full card numbers, card security codes, PINs, or sensitive card authentication data. Such information is processed directly by the relevant payment provider through secure and protected payment infrastructure.
A payment may be declined, delayed, blocked, or subject to additional verification by the customer’s bank, card issuer, payment provider, acquiring bank, crypto payment processor, or compliance provider. FINAP is not responsible for payment declines, delays, restrictions, or failures caused by third-party payment processors, banks, card issuers, payment networks, blockchain networks, compliance checks, sanctions screening, fraud prevention systems, or insufficient customer funds.
4. Account Balance
Payments made by customers are credited to the customer’s FINAP account balance after successful receipt and confirmation of funds.
The account balance is a prepaid service balance and may be used only for consuming FINAP Services.
The account balance:
1. is not a bank account;
2. is not an electronic money account;
3. is not a payment account;
4. does not represent stored value issued by FINAP;
5. does not earn interest;
6. is not transferable to another person or entity unless expressly approved by FINAP;
7. cannot be withdrawn as fiat currency;
8. cannot be withdrawn as cryptocurrency;
9. cannot be exchanged for cash or any financial instrument;
10. may only be used for services available within the FINAP platform.
FINAP does not hold customer funds for payment services or financial services purposes. Funds added to a balance represent prepayment for software, API, data intelligence, validation, and technology services only.
5. Free Monthly Requests
FINAP provides each eligible user with 100 free API requests per month for the purpose of testing, evaluating, and verifying the functionality of the platform before purchasing paid usage.
The free monthly allocation allows customers to assess the quality, suitability, technical performance, response format, and integration requirements of FINAP Services before adding funds to their account balance.
Once the free monthly allocation has been used, further API usage is charged according to the applicable pricing shown on the FINAP platform, website, pricing page, invoice, or commercial agreement.
Unless otherwise stated, paid API usage is charged at EUR 0.01 per API request and deducted from the customer’s prepaid balance.
6. Use of Balance and Service Suspension
Paid API usage is deducted automatically from the customer’s account balance based on actual service consumption.
If the customer’s balance is exhausted, insufficient, blocked, disputed, reversed, or otherwise unavailable, FINAP may automatically suspend access to paid Services until the customer adds sufficient funds.
FINAP is not responsible for any loss, interruption, failed request, failed integration, business delay, operational impact, or customer-side loss caused by insufficient account balance or suspended service access.
7. No Refund Policy
All payments, top-ups, prepaid balances, API request packages, and service purchases are final and non-refundable, except where a refund is required by applicable law or expressly approved by FINAP in writing.
Refunds are not provided because:
1. customers receive 100 free API requests per month to test and evaluate the Services before making any payment;
2. payments are made to purchase prepaid access to software and API services;
3. API services are digital services that may be consumed immediately after balance activation;
4. FINAP incurs infrastructure, provider, processing, data access, and operational costs when making Services available;
5. account balances are intended exclusively for consumption within the FINAP platform.
Customers are responsible for reviewing the Services, documentation, pricing, response formats, technical limitations, data limitations, and suitability before adding funds to their account.
Adding funds to the account balance confirms the customer’s intention to purchase FINAP Services and acceptance that such funds are non-refundable.
8. Chargebacks, Payment Reversals and Disputes
Customers must not initiate chargebacks, payment reversals, unjustified disputes, or payment cancellation requests after purchasing FINAP Services, except in cases of proven unauthorised payment, fraud, or clear billing error.
FINAP reserves the right to dispute and challenge any chargeback, reversal, payment dispute, or refund claim where the payment was made for legitimate prepaid access to FINAP Services.
Chargebacks are not accepted as a valid method of cancelling purchased Services because:
1. customers are provided with free monthly API requests to test the system before payment;
2. all paid balances are credited for software and API service usage;
3. the customer receives access to digital services immediately after successful payment;
4. FINAP does not sell physical goods that can be returned;
5. balances are used only inside the platform and cannot be withdrawn;
6. all pricing and usage conditions are disclosed before purchase;
7. the customer is responsible for deciding whether to top up the balance.
If a customer initiates an unjustified chargeback or payment reversal, FINAP may:
1. suspend or terminate the customer’s account;
2. revoke API keys;
3. block access to the platform;
4. deduct the disputed amount from the account balance;
5. charge the customer for chargeback fees, payment processor fees, bank fees, administrative costs, and legal costs where permitted by law;
6. provide evidence to the payment provider, acquiring bank, card issuer, or relevant authority showing account activity, payment records, API usage, acceptance of Terms, balance crediting, service access, IP logs, and technical usage data.
FINAP reserves the right to refuse future service to customers who submit abusive, fraudulent, or unjustified chargebacks.
9. Cryptocurrency Payments
Where cryptocurrency payments are accepted, such payments may be processed by third-party crypto payment processors or blockchain payment providers.
Cryptocurrency payments may be subject to network confirmations, blockchain fees, exchange rate fluctuations, provider fees, sanctions screening, wallet screening, AML checks, and compliance review.
A cryptocurrency payment is considered completed only after FINAP or its payment provider confirms successful receipt and allocation of funds.
Customers are responsible for ensuring that they send the correct cryptocurrency, amount, network, wallet address, memo, tag, or payment reference where applicable.
FINAP is not responsible for losses caused by incorrect wallet addresses, wrong blockchain networks, missing tags or memos, insufficient confirmations, blockchain congestion, network fees, third-party wallet issues, exchange rate volatility, or transactions sent outside the required payment instructions.
Cryptocurrency payments are final and non-refundable except where required by law or expressly agreed by FINAP in writing.
10. SEPA Bank Transfers
Where SEPA bank transfer is available, customers must include the correct payment reference, invoice number, account identifier, or other required details provided by FINAP.
FINAP may be unable to credit payments that are received without sufficient identifying information.
SEPA transfers may take time to arrive depending on the sending bank, receiving bank, payment scheme, banking hours, compliance review, intermediary processing, and other factors outside FINAP’s control.
FINAP may reject, return, or refuse a bank transfer where required for compliance, sanctions, AML, fraud prevention, operational, banking, or legal reasons.
11. Failed, Delayed or Rejected Payments
FINAP is not responsible for failed, delayed, rejected, reversed, blocked, or held payments caused by:
1. banks;
2. card issuers;
3. payment processors;
4. acquiring banks;
5. crypto payment providers;
6. blockchain networks;
7. compliance checks;
8. sanctions screening;
9. fraud prevention systems;
10. incorrect payment details;
11. insufficient funds;
12. technical errors outside FINAP’s direct control.
If a payment fails or is rejected, the customer should contact the relevant bank, card issuer, wallet provider, payment provider, or FINAP support where appropriate.
12. Billing Records and Invoices
FINAP may issue invoices, receipts, payment confirmations, balance top-up confirmations, usage reports, or account statements through the platform or by email.
Customers are responsible for maintaining accurate billing information and downloading or requesting any required invoices for their own accounting, tax, and business records.
FINAP may correct billing errors, adjust balances, reverse duplicate credits, or amend invoices where necessary to reflect accurate payment and service usage records.
13. Fraud Prevention and Payment Monitoring
FINAP and its payment providers may monitor payments, account activity, IP addresses, payment methods, device information, customer details, and transaction patterns for fraud prevention, sanctions compliance, AML compliance, cybersecurity, and abuse prevention purposes.
FINAP may refuse, delay, review, suspend, or cancel a payment or account balance top-up where the payment appears suspicious, fraudulent, unauthorised, sanctioned, high-risk, or inconsistent with the customer’s account profile.
FINAP may request additional information or documentation before crediting a payment or continuing service access.