# Embed a Claim Button
Add a "Claim Credential" button to any webpage — a course completion page, an event landing page, an onboarding flow. When a user clicks it, a polished modal walks them through email verification and deposits the credential directly into their LearnCard wallet.
{% hint style="info" %}
This is for **external websites** that want to award credentials to visitors. If you're building an app that runs *inside* the LearnCard App Store, see [Connect an Embedded App](/how-to-guides/connect-systems/connect-an-embedded-app.md) instead.
{% endhint %}
## Prerequisites
* A LearnCard developer account with an **Embed** integration created in the [Developer Dashboard](https://learncard.app)
* At least one **credential template** attached to that integration
* Your integration's **publishable key** (`pk_...`)
## Step 1: Create Your Integration & Template
1. Go to the Developer Dashboard → **New Integration** → choose **Embed Claim Button**
2. Follow the setup guide: set your partner name, create a credential template
3. Copy your **publishable key** from the Embed Code tab
## Step 2: Add the SDK
{% tabs %}
{% tab title="Script Tag (CDN)" %}
```html
```
{% endtab %}
{% tab title="npm/ESM" %}
```bash
npm install @learncard/embed-sdk
```
```js
import { init } from '@learncard/embed-sdk';
```
{% endtab %}
{% endtabs %}
## Step 3: Initialize the SDK
Add a target element and call `init()`:
```html
```
The credential name must match a template you created in the dashboard. The SDK resolves it server-side — you don't need to embed the full credential JSON.
## Step 4: Customize Branding (Optional)
```js
LearnCard.init({
publishableKey: 'pk_your_key_here',
target: '#claim-credential',
credential: { name: 'Course Completion' },
partnerName: 'Learning Economy Academy',
branding: {
primaryColor: '#1F51FF', // Button + stepper color
accentColor: '#0F3BD9', // Hover states
partnerLogoUrl: 'https://your-org.com/logo.png',
walletUrl: 'https://app.learncard.com',
},
});
```
## Step 5: Handle Success (Optional)
By default, after claiming, the SDK opens the wallet in a new tab (deep-linked to the credential via `handoffUrl`) and shows a success screen. You can hook into this with `onSuccess`:
```js
LearnCard.init({
publishableKey: 'pk_your_key_here',
target: '#claim-credential',
credential: { name: 'Course Completion' },
onSuccess: ({ credentialId, handoffUrl }) => {
// Runs in addition to the wallet auto-open
document.getElementById('success-message').style.display = 'block';
},
});
```
To suppress the automatic wallet redirect entirely, set `branding.walletUrl: ''`:
````js
LearnCard.init({
publishableKey: 'pk_your_key_here',
target: '#claim-credential',
credential: { name: 'Course Completion' },
branding: { walletUrl: '' }, // Disable auto-open
onSuccess: ({ credentialId, handoffUrl }) => {
// You fully control what happens next
document.getElementById('success-message').style.display = 'block';
},
});
## Complete Example
```html
Course Complete
Congratulations! You finished the course.
Claim your credential to add it to your LearnCard wallet.
✅ Credential claimed! Check your LearnCard wallet.
````
## Claim Flow
```mermaid
sequenceDiagram
participant User
participant Modal as Claim Modal
participant API as LearnCard API
participant Wallet as User Wallet
User->>Modal: Clicks Claim Credential
Note over Modal: Step 1 — Email View
User->>Modal: Enters email address
Modal->>API: POST /contact-methods/challenge
API-->>User: OTP sent to email
Note over Modal: Step 2 — OTP View
User->>Modal: Enters 6-digit code
Modal->>API: POST /contact-methods/verify
API-->>Modal: Session JWT
Note over Modal: Step 3 — Accept View
User->>Modal: Clicks Accept Credential
Modal->>API: POST /inbox/claim with JWT
API->>Wallet: Issue and store credential
Note over Modal: Success — confetti + checkmark
Modal->>User: View My LearnCard button
```
## Whitelisted Domains
For security, the API only accepts claims from domains you've whitelisted in the Embed Code tab of your dashboard. Add your production domain before going live.
During local development, `localhost` is allowed automatically.
## Testing Locally
Use the included embed example to test without a real backend:
```bash
# From repo root
pnpm --filter @learncard/embed-sdk build
cd examples/embed-example && pnpm dev
```
| URL | Mode |
| --------------------------------------------------------------- | ---------------------------------------------------- |
| `http://localhost:4321` | Stub mode — no backend, flows all the way to success |
| `?pk=pk_xxx` | Live network |
| `?pk=pk_xxx&template=My+Template` | Live network + template by name |
| `?pk=pk_xxx&api=http://localhost:4000/api&template=My+Template` | Fully local |
## Troubleshooting
**"This integration could not be found"** Your `publishableKey` doesn't match any active integration on the network. Double-check the key from your dashboard Embed Code tab and ensure your domain is whitelisted.
**Credential not appearing after claim** The credential lands in the user's inbox and is finalized when they next open their wallet. If you need to verify immediately, check the dashboard's activity tab.
**OTP not arriving** In local dev, check your brain-service logs — OTP codes are printed there when no email provider is configured.
## See Also
* [Embed SDK Reference](/sdks/embed-sdk.md)
* [Embed Code Tab (Dashboard)](/how-to-guides/connect-systems/connect-a-website.md)
* [Connect an Embedded App](/how-to-guides/connect-systems/connect-an-embedded-app.md) — for apps inside LearnCard
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.learncard.com/how-to-guides/connect-systems/embed-a-claim-button.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.