Become a Malartu merchant

Anonymous shipping for your store, in minutes. Merchant onboarding uses business/public information only — never personal customer data.

License & endpoint

License / API key	`lts-api-key-malartu`
Endpoint	`https://malartu.exchange/lts`
Client	`@aithne/ppil-client` — configured under `malartu.ltsUrl`
Auth envelope	API key header + non-empty `correlationId` header (idempotency); tokens in request bodies only, masked, never logged

The three logistics flows

Flow	Method + path	Body
`estimateShipping`	`POST /lts/ppil/logistics/estimate-shipping`	`{ pptId, cart, commToken?, addrToken? }`
`createShipment`	`POST /lts/ppil/logistics/create-shipment`	`{ pptId, shipmentDetails, commToken?, addrToken? }`
`startReturn`	`POST /lts/ppil/logistics/return`	`{ pptId, returnDetails, commToken?, addrToken? }`

The wallet supplies the tokens at checkout; your hooks sign with your keys, held under your control (HSM/external signing). Malartu verifies tokens server-side. The merchant never sees a customer's routing details — only token references.

Client config example

// aithne-ppil-client-config.json
{
  "malartu": {
    "ltsUrl": "https://malartu.exchange/lts"
  },
  "apiKeys": {
    "malartu": "lts-api-key-malartu"
  }
}

Zero PII applies to merchants too: you never handle, store, or forward customer personal data. Tokens only. Trust & compliance