Creator Shield
Creator Shield is a continuous monitoring capability designed for platforms where creators receive payments. As creators receive funds through card_receive or bank_account_receive, frameOS checks adverse media sources and Frame's proprietary risk indexes to detect activity that violates platform terms or poses legal or reputational risk.
If a creator is flagged, incoming transactions are blocked and your platform is notified with the account status and reason — so you can act quickly without waiting for a chargeback or regulatory notice to surface the problem.
Creator Shield requires KYC to be verified before it becomes active. Identity verification is the foundation of the monitoring — without a verified individual on the account, Creator Shield cannot run.
How it works
Once KYC passes and the account is active, Creator Shield runs in the background on every inbound payment. There is nothing the account holder needs to do — the checks are invisible to creators during normal operation.
When a payment is initiated to the account, frameOS evaluates the creator against:
- Adverse media — checks across news, legal, and public record sources for coverage tied to illegal or prohibited activity
- Frame's proprietary risk indexes — internal signals built from transaction patterns, platform history, and behavioral data across the Frame network
If a match is found that indicates the creator is engaging in activity that would bring risk to your platform, the transaction is blocked before it settles and the account is restricted.
Account restriction
When Creator Shield flags an account, incoming transactions are blocked and the account is marked as restricted in your Frame dashboard. The restriction reason is visible in the dashboard so you have immediate context on why the account was flagged.
Frame's risk operations team will reach out to your platform directly to walk through the restriction and determine next steps. Restrictions are not resolved through the API — all remediation is handled in coordination with the Frame team.
Restrictions are applied at the account level. All inbound payments to a restricted account are blocked until the restriction is resolved with Frame's risk operations team.
Required information
Creator Shield requires a complete individual profile from KYC. The following fields must be present on the account before the capability can become active:
| Field | Description |
|---|---|
| First name | Legal first name |
| Last name | Legal last name |
| Phone number | Account holder's phone number |
| Date of birth | Used for identity verification |
| Last 4 of SSN | Required as part of KYC |
| Address | Full residential address including street, city, state, postal code, and country |
If any of these fields are missing, Creator Shield will not activate. Ensure KYC is fully completed before expecting Creator Shield to become active.
Relationship to KYC
Creator Shield depends on a verified KYC record. Requesting creator_shield automatically includes KYC in the onboarding flow — you do not need to add kyc separately, though you can include it explicitly if you prefer.
The identity data collected during KYC — name, address, SSN, and date of birth — is what anchors the adverse media and risk index checks to the correct individual. Without a complete, verified identity, Creator Shield cannot evaluate the account.
Use KYC Prefill to pre-populate verified identity data from a phone number, reducing onboarding friction for creators while ensuring the identity checks are anchored to verified data.
Create an account with Creator Shield
Parameters
Must be individual. Creator Shield is only supported for individual accounts.
Include creator_shield to enable monitoring. KYC is automatically included — you do not need to add it separately. Include card_receive or bank_account_receive to enable the payment capabilities Creator Shield monitors.
The creator's email address.
The creator's first name.
The creator's last name.
Object containing number and country_code for the creator's phone.
curl --request POST \
--url https://api.framepayments.com/v1/accounts \
--header 'Authorization: Bearer API_KEY' \
--header 'Content-Type: application/json' \
--data '{
"type": "individual",
"capabilities": ["creator_shield", "card_receive"],
"profile": {
"individual": {
"email": "creator@example.com",
"name": {
"first_name": "Marcia",
"last_name": "Longo"
},
"phone": {
"number": "3107484186",
"country_code": "1"
}
}
}
}'
{
"id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"object": "account",
"type": "individual",
"status": "pending",
"external_id": null,
"capabilities": [
{
"id": "a1b2c3d4-e5f6-7890-abcd-ef1234567891",
"object": "capability",
"name": "kyc",
"status": "pending",
"disabled_reason": null,
"currently_due": [],
"disabled": null
},
{
"id": "a1b2c3d4-e5f6-7890-abcd-ef1234567892",
"object": "capability",
"name": "creator_shield",
"status": "pending",
"disabled_reason": null,
"currently_due": [],
"disabled": null
},
{
"id": "a1b2c3d4-e5f6-7890-abcd-ef1234567893",
"object": "capability",
"name": "card_receive",
"status": "pending",
"disabled_reason": null,
"currently_due": [],
"disabled": null
}
],
"profile": {
"individual": {
"email": "creator@example.com",
"ssn_last_four": null,
"name": {
"first_name": "Marcia",
"middle_name": null,
"last_name": "Longo",
"suffix": null
},
"phone": {
"number": "3107484186",
"country_code": "1"
},
"birthdate": null,
"address": null
}
},
"terms_of_service": null,
"metadata": {},
"livemode": false,
"created": 1721010605
}
Complete onboarding
Create an onboarding session to collect and verify the creator's identity. Creator Shield becomes active once KYC passes — no additional onboarding steps are required.
curl --request POST \
--url https://api.framepayments.com/v1/onboarding_sessions \
--header 'Authorization: Bearer API_KEY' \
--header 'Content-Type: application/json' \
--data '{
"account_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"return_url": "https://example.com/onboarding/complete"
}'
After onboarding completes, retrieve the account to confirm creator_shield has transitioned to active. From that point, all inbound payments are monitored automatically.