Issue to Earn
- Time to read: 10 minutes
- Time to implement: 1-3 hours
If your company verifies user identities, you can issue digital ID cards to those users and earn passive revenue when they're used.
Doing so requires only two things:
- Get user consent
- Issue credentials to user (1 API call)
To test in our sandbox environment, you can use our test brand and user:
Test Brand API Credentials
yVg3LEnF08y0MDmpHcPxB+sZWFcDARmPRKdY2M906ng=
https://core-api.sandbox-verifiedinc.com
To get an API key for your own brand, email us at Support@Verified.Inc.
Test User Login Credentials
+10123456789
richard@piedpiper.net
111111
These are Hooli and Richard Hendricks — yes, the ones from Silicon Valley! 😂
How It Works
User Experience
Try our Issue to Earn demos to see this user experience in action.
A user only needs to click 1 button to receive a digital ID card. (When they do, you make 1 API call behind the scenes.) It all takes less than 1 second!
Specifically, the user experience is:
- See prompt to activate ID card (e.g. a button)
- Give consent (e.g. click button)
- Receive email showing new ID card
The prompt is often a button, as in our Next User Sign In, Marketing Email, and In App Offer demos. But it can also take other forms — like a checkbox, as in our After User Sign Up demo.
This ID card is a purely digital one, and it has your brand on it. When you're ready for an API key for your brand, we will create an ID card design for you (or use one you send us).
Implement
Try our Issue to Earn demos to see example implementations. These are open source, so feel free to use the source code as a reference.
You can issue an ID card to a user in many ways. All of them involve the same two steps:
- Get user consent
- Issue credentials to user (1 API call)
1. Get User Consent
You must get a user's consent before issuing them an ID card. Not doing so violates our terms and will prevent us from paying you when the card is used.
Prompt the user to activate their digital ID card (from your brand). You can use a button prompt, as in our Next User Sign In, Marketing Email, and In App Offer demos. Or you can use another type of prompt — like a checkbox, as in our After User Sign Up demo.
Include this legal language:
By
TAKING_THIS_ACTION, I directYOUR_BRAND_NAMEto use Verified Inc. to create a digital ID card with my personal information, and I agree to Verified Inc.’s Terms of Use and acknowledge its Privacy Policy.
- Replace
TAKING_THIS_ACTIONwith language appropriate to the nature of your prompt. For example, if your prompt is an Activate button, you could replaceTAKING_THIS_ACTIONwith:clicking "Activate"
- Replace
YOUR_BRAND_NAMEwith, well, your brand name! - Make "Terms of Use" and "Privacy Policy" underlined or colored and hyperlinked to
https://www.verified.inc/legal#terms-of-useandhttps://www.verified.inc/legal#privacy-policy(respectively).
Here's full example:
By clicking "Activate", I direct Hooli to use Verified Inc. to create a digital ID card with my personal information, and I agree to Verified Inc.’s Terms of Use and acknowledge its Privacy Policy.
2. Issue Credentials to User
We define a digital ID card as a collection of credentials, issued by a brand to a user. We defined a credential as a piece of data about a user — like their phone number, address, or government ID.
To "issue an ID card" is just to issue credentials to a user for the first time. (To "update an ID card" is just to issue subsequent credentials to that user.)
Call POST /credentials with a user identifier (a verified email or phone for the user) and one or more credentials. For each credential, include a type and data in accordance with one of our data schemas.
If we don't have a data schema that suits your needs, email us at Support@Verified.Inc) and we'll make one for you.
For example, if you have a verified Social Security Number (SSN) and a full name for a user, you can issue them credentials. Just call POST /credentials with the user's email or phone, the SsnCredential and FullNameCredential type, and the SSN and full name data:
{
"email": "test@example.com",
"credentials": [
{
"type": "SsnCredential",
// based on the properties attribute of the schema
// single object, not an array of objects, since Ssn is an atomic credential
"data": {
"ssn": "111223333"
},
"expirationDate": 1893484800000
},
{
"type": "FullNameCredential",
// based on the properties attribute of the schema
// an array of objects, not a single object, since FullName is a composite credential
"data": [
{
"type": "FirstNameCredential",
"data": {
"firstName": "Richard"
}
},
{
"type": "LastNameCredential",
"data": {
"lastName": "Hendricks"
}
}
]
}
]
}
The credential data must be formatted according to the properties attribute of the credential type's schema definition. Please see our data schema library for more information.
(optional) Enable Affiliate Offers
The Implement section above describes how to implement standard issuance of ID cards. With standard issuance, you issue an ID card to a user, and that's it. There are no further steps.
But you can also implement partner issuance to enable affiliate offers for partner brands. With partner issuance, you issue an ID card to a user, and then you redirect them to a 1-Click Signup flow for the partner brand. That way, the user can immediately use their ID card to sign up for the partner, and you immediately earn revenue!
This allows you to present users with affiliate offers that convert with 1-click, meaning far higher conversion for partners and far more revenue for you.
Brands in our network that have implemented partner issuance have seen on average 7.9x higher conversion rates compared with normal affiliate offers.
If you'd like to enable partner issuance for your brand, email us at Support@Verified.Inc.