On‑Prem (Self‑Hosted) Setup
If you run Paylisher on‑prem (your own Engage instance), you own the entire Huawei stack — account, project, credentials, and backend configuration. This page is the end‑to‑end checklist; each step links to its full instructions.
Customers on Paylisher's hosted services do not do the account/backend steps — Paylisher does. They only integrate the app (steps 6). See the Overview audience table.
End‑to‑end checklist
| # | Step | Where | Details |
|---|---|---|---|
| 1 | Create an enterprise Huawei developer account | Huawei console | [AppGallery Setup §1](../../Push Credentials/huawei-hms.md) |
| 2 | Create an AppGallery Connect project (one project, many apps) | AGC | [§2](../../Push Credentials/huawei-hms.md) |
| 3 | Add your Android app (package = applicationId) | AGC | [§3](../../Push Credentials/huawei-hms.md) |
| 4 | Register the SHA‑256 fingerprint (debug + release) | AGC | [§4](../../Push Credentials/huawei-hms.md) |
| 5 | Enable Push Kit + download agconnect-services.json | AGC | [§5–6](../../Push Credentials/huawei-hms.md) |
| 6 | App‑side integration (module, Maven repo, AGConnect plugin, config, token) | Your app | App Integration |
| 7 | Obtain the sending credential (API client, project‑level) | AGC | [§7](../../Push Credentials/huawei-hms.md) |
| 8 | Set the HMS_* env variables on your Engage instance | Engage | Backend Config |
| 9 | Verify with a dry‑run, then real delivery via Cloud Debugging | Engage / Huawei | Backend Config, Troubleshooting |
What you own vs. what Paylisher provides
| On‑prem (you) | Hosted (Paylisher) | |
|---|---|---|
| Huawei account + AGC project | ✅ yours | Paylisher's |
App registration + SHA‑256 + agconnect-services.json | ✅ yours | coordinate with Paylisher |
Sending credential (HMS_*) | ✅ yours, in your Engage | Paylisher's |
| App‑side SDK integration | ✅ | ✅ |
Minimal config recap
Once the account side is done, on‑prem Engage needs just these (v2/central):
HMS_PROJECT_ID=...
HMS_CLIENT_ID=...
HMS_CLIENT_SECRET=...
No JSON key file, no PEM — HMS is env‑only on the backend. FCM is unaffected; if these are left empty, HMS is simply disabled.
Recommended order
The account/verification step (1) is the long pole (verification takes 1–2 business days, and a DUNS number — if you don't already have one — can take weeks). Start it first; the app‑side integration (6) can proceed in parallel and be verified device‑free via the client simulation and dry‑run described in Troubleshooting.