Merchant Portal setup

12. Merchant Portal setup

Merchant Portal is DLT's own frontend counterpart to the DLT backend/back office. It belongs to the DLT ecosystem and lets DLT merchants manage their accounts; it is separate from websites, mobile apps and server integrations owned by those merchants.

In this guide, merchant means a business registered with DLT. Its Administrator and Developer users sign into DLT Merchant Portal to manage their account. Developers building that business's own server integration should use the separate Merchant integrations guide.

Before implementing DLT Merchant Portal, the DLT Portal development team needs:

• Test/production API origins and deployed endpoint availability.
• DLT Merchant Portal ecosystem application ID/secret, application code, allowed origins and merchant-portal scope, held only by the DLT Merchant Portal backend.
• Configured DLT Merchant Portal URL (APP_MERCHANT_URL), working reset/verification/invitation emails and public logo URLs.
• Supported currency catalogue, timestamp conventions and synthetic Administrator/Developer accounts with test transactions.

For currency options, public GET /api/v1/json/currency returns success/message/data with catalogue items whose currency code is cc. Other display fields are deployment data. It uses public/API throttles and its own failure behavior.

Within the DLT ecosystem, Merchant Portal implements its backend session, browser cookies/CSRF, forms, role-aware UI, reset page and invitation page. The DLT backend API enforces authorization, merchant isolation, financial state and evidence policy. Collection actions, refunds, replay, multi-merchant switching, exports and streaming are outside this contract.

12.1 Currency lookup request validation

These tables reflect the current implementation’s request rules. See input conventions for required/optional/null behavior and error formats.

Validation: GET /api/v1/json/currency

Send no request body. This public lookup accepts no documented body/query inputs. The controller reads the catalogue without validating request fields; extra inputs do not filter it.