Holyprices Billing

This is a service endpoint, not a website. It is the shared billing layer that Holyprices products call — plans, subscriptions, payments and payment-gateway settings.

This page does not mean the service is running. nginx serves it straight from disk, so it appears even when the billing container is stopped. The only real check is /health, which must answer {"status":"ok"}.

What lives here

/health
Liveness. The authoritative check.
/admin/…
Platform-admin API — products, plans, accounts, payments, gateway settings. API only; there is no console UI yet, so a browser gets 404 from the application on /admin/ itself. That 404 is the app answering, which means it is running.
/webhooks/…, /callback_url
Where PayPal, Flutterwave and AzamPay call in.

Deliberately not public

/v1/… is the product-to-billing API. Products reach it over the internal network, never the internet, so a leaked service API key is useless from outside the server. The API docs are closed for the same reason — read them through an SSH tunnel:

ssh -L 9030:127.0.0.1:9030 root@<server>
# then open http://127.0.0.1:9030/docs

Both return 404 here. That is correct, not a fault.