Setting Up Your Issuer Profile
Your Issuer Profile is the identity that appears on every certificate you issue and on the public verification page seen by recipients and third parties.
Go to Issuer in the sidebar to access it.
Initial Setup Wizard
If you have never configured your issuer before, Credenza will walk you through a two-step setup wizard the first time you visit the Issuer page.
Step 1: Profile Details
| Field | Notes |
|---|---|
| Logo | Upload a JPEG, PNG, or WebP image (max 500 KB). Drag and drop or click to browse. Appears on the verification page and optionally in your certificate design. |
| Issuer Name | The name of your organisation or institution as it should appear on certificates and the verification page. |
| Description | A short description of your organisation. Shown on the public verification page. |
Step 2: Verification URL Slug
Choose the permanent slug for your public verification URL:
https://credenza.id/verify/your-slug-here
This slug is permanent. Once set, it cannot be changed. Choose something that reflects your organisation's name and will remain relevant long-term, for example
universitas-nusantaraorlembaga-sertifikasi-abc.
The slug must be:
- Lowercase letters, numbers, and hyphens only
- Unique across all Credenza accounts
After completing setup, every certificate you issue will include a QR code pointing to this URL.
Editing Your Profile
After initial setup, all fields except the slug can be updated at any time from the Issuer page.
Changes to the issuer name or logo will be reflected on the verification page immediately. They do not alter previously issued certificates. The PDF and blockchain record remain unchanged.
Custom Domain
You can serve your verification page from your own domain instead of credenza.id/verify/your-slug. This is optional but recommended for institutions that want full brand consistency.
Why Use a Custom Domain?
- Brand trust: recipients and verifiers see your own domain (e.g.
verify.yourcompany.com) instead of a third-party URL, which strengthens credibility - Professional appearance: QR codes on certificates point to your domain, reinforcing your organisation's identity
- Consistency: all touchpoints (certificates, verification pages, and emails) carry your brand
Prerequisites
Before setting up a custom domain, you need:
- A completed issuer profile: you must have already set your verification slug
- An active domain subscription: custom domains require a paid subscription (see below)
- Access to your DNS provider: you need to be able to create DNS records for your domain (e.g. Cloudflare, GoDaddy, Namecheap, etc.)
Buying a Domain Subscription
Custom domains are a subscription feature. You need an active subscription to add and use a custom domain.
Step-by-step: Purchase a Domain Subscription
- Open Issuer from the sidebar
- Scroll to the Domain Subscription section
- If you have no active subscription, you will see a Subscribe button. Click it
- If you already have an active subscription but want to extend it, click Extend
- A package selection grid appears. Choose your preferred duration (e.g. 1 month, 3 months, 6 months, 12 months)
- Click Purchase
- You are redirected to the payment gateway. Complete payment using your preferred method
- After payment, you are redirected back to Credenza:
- Success: your subscription is activated immediately
- Failed: no subscription is created, you can try again
Subscription Stacking
You can purchase multiple subscriptions and they stack. Each new purchase extends your expiry date from the current end date, not from the purchase date. For example:
- Your subscription expires on June 30
- You buy a 3-month extension on June 15
- Your new expiry date becomes September 30 (June 30 + 3 months)
This means you can buy ahead without losing any time.
Subscription Status
The subscription section shows your current status:
| Status | Meaning |
|---|---|
| Active until ... | Your subscription is live and your custom domain is functional |
| Expires in X days | Your subscription is about to expire, consider extending |
| Expired | Your subscription has ended, custom domain no longer works |
| No subscription | You have never purchased a domain subscription |
What Happens When a Subscription Expires?
When your domain subscription expires:
- Your custom domain stops working. Visitors to your custom domain see an expiry notice with a fallback link to
credenza.id/verify/your-slug - Your certificates and verification page remain fully accessible via the default
credenza.id/verify/your-slugURL - Your domain configuration (the domain name and DNS verification) is preserved. You do not need to reconfigure it if you renew later
- Simply purchase a new subscription to reactivate your custom domain
Redeeming a Domain Claim Code
If you have a promotional code for a free domain subscription:
- In the Issuer page, scroll to the Claim Code section under Domain Subscription
- Type the code into the input field
- Click Redeem
- Your subscription is activated instantly. A confirmation toast shows the duration added
Claim codes follow the same rules as credit claim codes: not case-sensitive, limited total redemptions, one use per issuer.
Handling Pending Payments
If you close the browser before completing payment, the invoice stays Pending in your purchase history:
- Scroll to the Active & Pending history section on the Issuer page
- Find the pending row
- Click Check / Pay Now
- If already paid on the gateway side, your subscription activates immediately
- If still pending, you are redirected to complete payment
Setting Up Your Custom Domain
Once you have an active domain subscription, you can configure your custom domain.
Step-by-step: Add and Verify a Custom Domain
-
In the Issuer page, scroll to the Custom Domain section
-
Enter your desired domain, for example:
verify.yourcompany.comUse a subdomain like
verifyorcerts. Do not use your root domain. -
Click Add Domain
-
You will see DNS setup instructions. In your DNS provider, create a CNAME record:
Field Value Host / Name verify(or whatever subdomain you chose)Record Type CNAMEPoints to / Value credenza.idTTL 3600(or your provider's default) -
Wait for DNS propagation. This is usually a few minutes but can take up to 48 hours
-
Back in Credenza, click Verify Custom Domain
-
Credenza checks your DNS records and marks the domain as Verified once the CNAME is detected
Domain Status Badges
| Badge | Meaning |
|---|---|
| Verified | DNS is correctly configured and the custom domain is live |
| Pending | The CNAME record has not been detected yet. Check your DNS settings and try again |
Common DNS Setup Examples
Cloudflare:
- Log in to Cloudflare, select your domain
- Go to DNS > Records
- Click Add record, Type: CNAME, Name:
verify, Target:credenza.id - Set Proxy status to DNS only (grey cloud). Do not proxy through Cloudflare
GoDaddy:
- Log in > My Products > select your domain > DNS
- Click Add, Type: CNAME, Name:
verify, Value:credenza.id, TTL: 1 hour
Namecheap:
- Log in > Domain List > Manage > Advanced DNS
- Click Add New Record, Type: CNAME, Host:
verify, Value:credenza.id, TTL: Automatic
Removing a Custom Domain
To remove your custom domain:
- In the Custom Domain section, click the trash icon next to your domain
- The domain is removed immediately
You can add a different domain at any time, as long as your subscription is active.
Troubleshooting
| Problem | Solution |
|---|---|
| Verification keeps saying "Pending" | Wait up to 48 hours for DNS propagation. Double-check CNAME target is exactly credenza.id |
| Domain works but shows HTTP errors | Ensure your CNAME is not proxied (Cloudflare users: use DNS-only / grey cloud mode) |
| Domain was working but stopped | Check if your domain subscription has expired. Renew it to reactivate |
| Want to change the domain | Remove the current domain first, then add the new one |
Organisation Issuer Profile
If you are working inside an Organisation, the Issuer page configures that organisation's issuer, not your personal one. Only organisation Owners can access and edit the organisation's issuer profile. Members cannot.
Domain subscriptions and custom domains are also scoped to the organisation. Each organisation manages its own domain independently.