Finlazo developers · Crypto acceptance
Website integration quick start
Prepare your ecommerce website or application for cryptocurrency payments without making assumptions about API availability or settlement.
Prepare a verified business account
Your business must complete its applicable onboarding and KYB requirements before payment acceptance can be enabled.
Create a unique reference for each website order
Store your own order ID and expected amount. Keep the amount, cryptocurrency, blockchain network and expiry together as one immutable payment request.
Handle payments on your server
When merchant API access is released, create payment requests from your website backend. Never put secret keys or signing credentials into browser code.
Show only approved payment instructions
Display the receiving address, network, QR code and expiration only after Finlazo confirms that the checkout route is ready.
Verify the final status before fulfilment
Treat a displayed transaction ID or initial detection as unconfirmed. Await authenticated, attributable final payment verification before delivering goods or services.
Prepare for exceptions
Design an order state for pending, partial, overpaid, expired and unallocated deposits. Do not automatically assume an amount match identifies an invoice.
Authentication and security
API keys must stay on your server. Future callback verification will need signed payload checks, idempotency and replay protection.
Testing before accepting payments
When a test environment is available, verify exact-payment, underpayment, overpayment, wrong-network, late-payment and duplicate-event scenarios before launch.
Understand the full payment lifecycle
For an architecture overview, visit the API Overview page. For availability, contact the Finlazo team directly.