Language

API Terms

Version 0.1.0Last updated: Jun 2, 2026

Overview

These starter API Terms describe rules for external merchants and websites integrating with ForgePay payment APIs in test mode and future live mode.

Legal review required

This is a starter template and must be reviewed by a qualified lawyer before commercial launch.

ForgePay is not a bank. ForgeCredit is an internal settlement unit for services available in the ForgePay ecosystem.
ForgePayforgepay.ai

API Terms

Version 0.1.0. Starter text for review and editing. Last updated: Jun 2, 2026.

This is a starter template and must be reviewed by a qualified lawyer before commercial launch.

These starter API Terms describe rules for external merchants and websites integrating with ForgePay payment APIs in test mode and future live mode.

Editable placeholder variables

  • [COMPANY_LEGAL_NAME]
  • [COMPANY_ADDRESS]
  • [COMPANY_REGISTRATION_NUMBER]
  • [VAT_ID]
  • [OWNER_NAME]
  • [CONTACT_EMAIL]
  • [SUPPORT_EMAIL]
  • [DPO_EMAIL]
  • [JURISDICTION]
  • [PAYMENT_PROVIDER]
  • [LAST_UPDATED_DATE]

Core ForgePay statements

  • ForgePay is not a bank.
  • ForgeCredit is not money issued by a government or central bank.
  • ForgeCredit is not a savings product.
  • ForgeCredit does not create ownership, yield or repayment rights.
  • Ordinary users cannot withdraw FGC to EUR.
  • Bonus FGC is non-transferable.
  • Transferable FGC may be sent between users subject to limits and fees.
  • The user-to-user transfer fee is 0.02%.
  • Sellers are settled according to Seller Terms.
  • External merchant API usage is governed by API Terms.

Merchant access

Merchants may create API keys, configure webhook endpoints and use one-time checkout sessions, subscription checkout sessions, refunds and settlement summary endpoints under these API Terms.

Security and secrets

API keys must be protected by merchants. ForgePay stores API key hashes and webhook HMAC verification should be used for event authenticity.

ForgeCode checkout

Hosted checkout must clearly show ForgePay, the merchant name, amount, payment type and recurring authorization details before the user confirms with ForgeCode and transaction PIN.

Idempotency and limits

API requests may require idempotency keys, rate limits and audit logs. Hidden recurring charges are not allowed.

No final legal advice

This page is starter content for drafting and product planning only. It must be reviewed and adapted by a qualified lawyer before commercial launch.