Changelog

You can now complete the domain ownership step of organization verification yourself through DNS, directly from Admin Center → Account. For a step-by-step walkthrough of the verification flow, see How to do organization verification.

To get started, click the Get Verified banner in Admin Center → Account. Wauld shows you the DNS record details you need - including record type, hostname, TXT value, and TTL. Add that record through your domain registrar, return to Wauld, and click Verify. If the record is in place and publicly available, Wauld confirms domain ownership automatically. Your organization then moves to Under Review while Wauld's team reviews your organization name, issuing authority, logo, verified domain, and other public details before approving your account and assigning a Verified status and badge.

What this means for you:

• Complete the domain ownership step yourself without waiting for extended manual verification back-and-forth

• Give recipients, employers, and institutions a clear signal that credentials come from a verified source

• Find the full verification setup in Admin Center → Account under the Get Verified banner

To understand what Verified status means for your organization and the credentials you issue, read Benefits of organization verification in Wauld.

Note: The Verified badge applies only to credentials issued after your organization is approved. Credentials issued before verification are not updated retroactively.

You can now include the credential PDF as an attachment in the credential delivery email. When issuing credentials, select the Attach credential PDF to email option in Issuing Options, and recipients receive both the credential access link and the attached PDF in the same email. The option is available for immediate and scheduled issuance, and also appears in the Resend Credential modal and the Edit Credential reissue flow.

What this means for you:

• Give recipients their credential PDF immediately in their inbox for formal submissions, compliance, or records

• Reach recipients whose organizations restrict external links by delivering the credential as a PDF attachment

• Stay in control of PDF delivery whether issuing, resending, or reissuing credentials

You can now connect Wauld with 9,000+ apps through Zapier, helping you bring credential issuance into the workflows your team already uses.

With this update, you can use events from other tools to issue credentials in Wauld, or use credential activity in Wauld to start follow-up actions elsewhere. This can support workflows such as issuing a credential after a course completion, form submission, webinar attendance, spreadsheet update, CRM status change, or other activity captured in your connected apps.

Wauld currently supports two Zapier events:

• Issue Credential - an action that lets you issue a credential in Wauld when something happens in another app.

• Credential Issued - a trigger that starts a workflow in another app after a credential is issued from Wauld.

We have also added Wauld Zap templates to help you start faster. These templates provide ready-made workflow structures for common credentialing use cases, so you can choose a relevant flow, map your recipient and credential data, and adjust it based on how your team works.

You can visit the Wauld app page on Zapier to explore available Wauld integrations, view Zap templates, and see the apps you can connect with Wauld.

To learn how to set up and use this integration, read the Wauld Zapier Integration Guide.

You can now set up custom triggers in Wauld to issue credentials from the systems and workflows your team already uses.

With this update, you can create a trigger for a specific document, set an expiry, and configure the credential issuance action. Once the trigger is created, Wauld generates a unique trigger URL for that document.

When the defined payload is sent to this URL, Wauld uses the submitted data to issue the credential automatically. This helps you turn actions from another system, such as a course completion, assessment result, event attendance, form submission, or internal approval, into credential issuance without adding recipients manually each time.

Custom triggers are useful when Wauld needs to be the final step in a broader workflow. Your external system can complete its own process first, then send the required data to Wauld so the right credential is issued from the right document.

This gives you a more flexible way to connect credential issuance with your existing processes, while keeping the credential design, document setup, and issuance configuration managed inside Wauld.

You can now add image attributes to your credential designs, giving you more flexibility to personalize credentials with recipient-specific visuals.

With this update, custom attributes can be created as either Text or Image attributes. Image attributes can be used for details such as profile photos, signatures, logos, ID photos, or other visuals that may be different for each recipient.

Once an image attribute is added to the Design Studio, you can place it on the canvas and resize it however you need. The image preserves its original aspect ratio and expands to fit the selected area, so it stays clean and consistent in the design.

You can also use the existing resizing, snapping, and layering options in the Design Studio to position image attributes more precisely and create better credential layouts. Before issuing, these images are shown in the credential preview, helping you review how each recipient’s credential will look.

This helps you create credentials that feel more personal, branded, and complete, while giving your recipients credentials that include the right visual details for their achievement or identity.

You can now use webhooks to send credential issuance data from Wauld to other systems automatically.

With this update, whenever a credential is issued, Wauld can send a structured payload to a webhook URL configured by your team. This helps you keep external systems updated, trigger follow-up workflows, and pass issuance details to the tools that need them.

The webhook payload includes key issuance information, such as issuer details, recipient details, credential details, and related issuance data. This allows your connected systems to understand who issued the credential, who received it, what was issued, and when the issuance happened.

Webhooks can be used to support workflows such as updating learner records, syncing issued credential details with a CRM, sending data to an internal reporting system, triggering notifications, starting an approval or follow-up process, or storing issuance activity in your own database.

This gives you more flexibility to use Wauld issuance data across the systems where your team already manages recipients, records, reporting, or follow-up actions.

You can review the sample webhook payload below to see what data is sent when a credential is issued:

You can now issue credentials through Wauld with alignment to the 1EdTech Open Badges 3.0 specification, giving your credentials a stronger standards-based foundation for verification, portability, and trust. Instead of being just a visual badge, each credential now carries structured achievement data in a format designed for broader compatibility across platforms and ecosystems.

With Open Badges 3.0 support, all credentials include structured metadata for the issuer, recipient, achievement, criteria, skills, evidence, and related context. That metadata is represented in JSON-LD format.

This gives issuers a more future-ready way to issue digital credentials and helps ensure achievements are represented in a format that is easier to validate and interpret across different platforms.

For recipients, this means the credentials they earn carry richer and more trustworthy information about what they achieved, who issued it, and what it represents. That makes credentials more meaningful when shared with employers, institutions, digital wallets, or other platforms, while also making it easier for others to understand and trust the achievement behind them.

Working with attributes in the Design Studio is now quicker and more intuitive.

Users can now add attributes directly by clicking on the attribute chips in the left-side panel. Image attributes are added straight to the canvas, while text attributes work in a more flexible way based on what the user is doing. If a user is typing inside a text box, the attribute is inserted right at the cursor position. If not, it is added as a new text box on the canvas.

This makes it easier to build credential designs faster, reduces extra steps while editing, and gives users a more natural way to place dynamic content exactly where they need it.