Getting Started with BadgeMax Pro
This guide walks through creating, signing, downloading, and publishing your first BadgeMax Pro badge.
Step 1 — Open the Badge Designer
The main interface contains:
- A badge preview
- Embed code
- Attestation metadata
- Badge appearance settings
- Logo settings
- Administrator key controls
- Static hosting export controls
On smaller screens, the preview is positioned before the designer controls.
Step 2 — Set the Assertion URL
Enter the URL where the badge's assertion JSON will be hosted.
Example:
https://example.com/a/<ID>.jsonBadgeMax Pro can replace <ID> with the generated badge identifier.
The assertion URL is also the destination of the checkmark link inside the badge.
Use a domain you control when issuing real badges.
Step 3 — Customize the Badge
Configure the visual settings.
| Setting | Default |
|---|---|
| Fingerprint Length | 18 |
| Font Size | 22 px |
| Background | #0f0f10 |
| Checkmark Background | #CEFFA8 |
| Text Color | #ffffff |
| Bevel Stroke | #ffffff |
| Label | Verified |
| Badge Width | 340 px |
| Logo Type | None |
The badge height is fixed at 72 pixels.
Step 4 — Add Branding
Choose one of three logo modes:
- None
- URL image
- Monogram
For a monogram, enter up to three characters.
For an image, supply a URL or select a local image file.
Step 5 — Prepare a Signing Key
In Keys (Admin), choose:
Generate P-256 Key
Alternatively, import an existing private JWK.
A signing key is required for generating a signed badge.
The application also creates a key automatically when needed.
Step 6 — Generate the Badge
Click:
Generate Badge
The application constructs the SVG, calculates its artwork hash, and signs the attestation.
It then attempts to verify the badge against the issuer's published JWKS.
Why Might It Say Unverified?
A newly generated badge may display Unverified because the public JWKS has not yet been published at the expected URL.
This does not necessarily mean that badge generation or signing failed.
The built-in verification check requires the remote issuer key to be available.
Step 7 — Download the Badge
Click:
Download badge.svg
The actual downloaded filename uses the badge identifier.
For example:
A1B2C3D4E5F6.svgThe SVG contains its attestation metadata.
Step 8 — Download the Public Keys
Click:
Download jwks.json
This exports a JSON Web Key Set containing a public verification key.
Do not publish the private JWK.
Step 9 — Download the Assertion
In Static Hosting Export:
- Choose active.
- Set optional expiry hours.
- Click Download
/a/<id>.json.
The file contains the badge's published status and a signature.
Step 10 — Publish the Files
Upload the exported files to your website.
Recommended structure:
/
├── .well-known/
│ └── bar/
│ └── jwks.json
├── a/
│ └── A1B2C3D4E5F6.json
└── badges/
└── A1B2C3D4E5F6.svgUse the actual generated identifier in each filename.
Step 11 — Verify
Download verify.html from BadgeMax Pro.
Host the page where it can access the badge and issuer resources.
Enter the published SVG URL and click Verify.
The verification page reports the checks performed.
Next Steps
Read the detailed guides for badge customization, key management, verification, and deployment.
Updated 7 days ago
