Enviroment

LedgerBlock currently provides a Production environment for API integrations.

The Production environment gives you access to LedgerBlock's live infrastructure and is used to process real transactions and interact with live customer and account data.

Production Environment

The Production environment is the live LedgerBlock environment. Requests made against this environment can perform actual operations, including transactions and other actions that affect real data.

Base URL

All Production API requests use the following base URL:

https://block.fuspay.finance

Endpoint Structure

LedgerBlock API endpoints are constructed by appending the endpoint path to the Production base URL.

For example, the documented endpoint:

GET /api/v1/utility/operators

is accessed using:

GET https://block.fuspay.finance/api/v1/utility/operators

Similarly:

POST /api/v1/payout/bank-list/verify

is accessed using:

POST https://block.fuspay.finance/api/v1/payout/bank-list/verify

Environment Availability

At this time, LedgerBlock provides the following environment:

There is currently no separate Staging or Sandbox environment.

Production Credentials

Production API requests require valid LedgerBlock authentication credentials.

Use the credentials provided for your merchant account when making requests. Authentication requirements vary by API operation and are specified on the relevant endpoint documentation.

Do not expose production credentials in:

• Frontend or client-side applications
• Public repositories
• Browser-based code
• Documentation examples
• Logs or error messages
• Publicly shared Postman collections

Store credentials securely on your backend or in a secrets-management system.

Working With Production

Because the Production environment operates on live infrastructure, integrations should be implemented carefully before making live requests.

When developing an integration:

1. Review the relevant API endpoint documentation.
2. Configure your server with the required Production credentials.
3. Use the Production base URL for API requests.
4. Send the required headers and request body.
5. Validate API responses and error handling.
6. Implement webhook handling where required.
7. Test your integration carefully before processing live customer transactions.

Production Data

Data created or modified through the Production API is treated as live data.

For example, operations involving:

• Users
• KYC records
• Wallets
• Accounts
• Transfers
• Payments
• Payouts
• Transactions

may create or modify real records.

Avoid using real customer information for development or experimentation unless the operation is intentionally being performed in Production.

API Versioning

LedgerBlock API endpoints include their API version in the URL path.

For example:

/api/v1/

A complete Production endpoint therefore follows this structure:

https://block.fuspay.finance/api/v1/{endpoint}

For example:

https://block.fuspay.finance/api/v1/utility/operators

The API version is part of the endpoint and should be preserved when making requests.

Quick Reference

Environment: Production

Base URL:

https://block.fuspay.finance

API Version: v1

Endpoint format:

https://block.fuspay.finance/api/v1/{endpoint}

Important: LedgerBlock currently does not provide a separate Sandbox or Staging environment. Production requests interact with the live system, so ensure your integration is properly configured before performing operations that create or modify live data.