Keep credentials on your server
Tokens belong in your secure environment. Never include them in website code, URLs or logs.
API & DEVELOPERS
Connect payments, currency accounts and Business data. From a Checkout button to APIs, build an experience that connects your product with your business operations.
/organizations/:id/checkoutFROM PRODUCT TO OPERATION
An online shop, a business tool, a platform: start with your customers’ journey and connect the operations that matter.
Retrieve or create the permanent Checkout for a destination account belonging to your business. The response includes its public link and integration snippets.
View reference 02Retrieve links attached to your business accounts. The kind parameter distinguishes payment links from Checkout.
View reference 03Connect your sales tracking to quotes, invoices and credit notes. Filter by status, document kind or customer within your organisation.
View reference 04Retrieve your business bank accounts and their currency. Each account statement is also available as JSON or CSV.
View referenceCLEAR CONNECTIONS
Explore existing Business routes. Examples use placeholder identifiers and do not trigger any operation.
/api/business/organizations/{orgId}/checkoutRetrieve or create the permanent Checkout for a destination account belonging to your business. The response includes its public link and integration snippets.
Owner, administrator or finance manager
curl --request POST \
'https://api.belook.com/api/business/organizations/<organization_id>/checkout' \
--header "Authorization: Bearer $BELOOK_ACCESS_TOKEN" \
--header 'Content-Type: application/json' \
--data '{"destination_account_id":"<account_id>"}'{
"success": true,
"data": {
"id": "<link_id>",
"currency": "EUR",
"status": "active",
"public_url": "https://pay.belook.com/pay/<link_code>",
"snippets": {
"link_with_amount": "https://pay.belook.com/pay/<link_code>?amount={MONTANT}&reference={REFERENCE}"
}
}
}Illustrative format excerpt. Values and additional fields depend on your account and the actual response.
These routes require a Belook user session and organisation permissions. For partner access or server-to-server integration, agree capabilities and authentication with our team.
CHECKOUT · BELOOK PAY
Choose a destination account in your Business space, then retrieve your Checkout link and HTML button. Add it to your website or share it with your customer.
<a href="https://pay.belook.com/pay/REMPLACEZ_PAR_VOTRE_CODE"
target="_blank" rel="noopener noreferrer"
style="background:#0A7D3B;color:white;padding:14px 24px;
border-radius:12px;display:inline-block;text-decoration:none">
Payer avec Belook Pay
</a>Always check the payment status in Belook before fulfilment. A customer returning to your website is not a payment confirmation.
Tokens belong in your secure environment. Never include them in website code, URLs or logs.
Each route checks active membership, authorised role and accessible modules. Account identifiers must belong to the target organisation.
Handle 401, 403, 409 and 429 errors. Partner webhooks, signatures and testing are scoped around the flows agreed with Belook.
Contact our Business team with your use case, markets and expected journeys. Scoping establishes access, documentation and capabilities for your partnership.
Integration scoping defines statuses and webhook exchanges. It also establishes exception handling and reconciliation for the agreed flows.
YOUR NEXT CONNECTION
Share your use case, markets and the flows to connect. Together, we define scope, access and validation steps.