Payment Currencies
PasspaymentCurrency as a token symbol (for example SOL), not a mint address. JUP is the default and transfers directly. SOL, USDC, and JUPUSD are converted to 1000 JUP via an Ultra swap.
paymentCurrency value | Resolves to mint | Decimals | Conversion |
|---|---|---|---|
JUP | JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN | 6 | Direct transfer of 1000 JUP |
SOL | So11111111111111111111111111111111111111112 | 9 | Swapped to 1000 JUP via Ultra |
USDC | EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v | 6 | Swapped to 1000 JUP via Ultra |
JUPUSD | JuprjznTrTSp2UFa3ZBUFgwdAmtZCq4MQCwysN55USD | 6 | Swapped to 1000 JUP via Ultra |
Prerequisites
- Get an API key at Portal. All requests require the
x-api-keyheader. - The submitting wallet needs enough of your chosen payment currency for 1000 JUP. Transactions are gasless, so the wallet does not need extra SOL for network fees.
Flow
The API is a three-step flow: check eligibility, craft a payment transaction, sign it, then execute.Step 1: Check Eligibility (Optional)
Check if the token can be submitted for verification and/or metadata updates. This step is optional since the execute step also rejects ineligible tokens before charging payment, but it keeps your flow clean and avoids unnecessary transaction crafting. The most common reason for ineligibility is an existing pending submission for the token.| Field | Type | Description |
|---|---|---|
tokenExists | boolean | Whether the token exists on-chain |
isVerified | boolean | Whether the token is already verified |
canVerify | boolean | Whether a verification request can be submitted |
canMetadata | boolean | Whether a metadata update can be submitted |
verificationError | string | Why verification cannot proceed (only present when there is a specific error) |
metadataError | string | Why metadata cannot proceed (only present when there is a specific error) |
canVerify and canMetadata are false, the submission will be rejected before any payment is charged.
Step 2: Craft the Payment Transaction
This returns an unsigned Solana transaction worth 1000 JUP. By default it crafts a direct JUP transfer. PasspaymentCurrency to pay in SOL, USDC, or JUPUSD instead, which crafts an Ultra swap to JUP (see Pay with SOL, USDC, or JUPUSD). Save the requestId from the response, you need it in the next step.
| Parameter | Type | Required | Description |
|---|---|---|---|
senderAddress | string | Yes | Solana wallet address that will sign and pay for the transaction |
paymentCurrency | string | No | Token symbol, not a mint address: JUP (default), SOL, USDC, or JUPUSD. Non-JUP currencies route through an Ultra swap to JUP. |
requestId that links this payment to your execute request.
| Field | Type | Description |
|---|---|---|
transaction | string | Base64-encoded unsigned transaction |
requestId | string | Unique ID for this payment. Pass to /execute. |
receiverAddress | string | Wallet address receiving the JUP payment |
mint | string | Mint of the JUP collected (always JUP) |
amount | string | JUP amount in smallest unit (1000 JUP = 1000000000) |
tokenDecimals | number | Decimals of the JUP collected (6) |
tokenUsdRate | number | USD rate of JUP at craft time |
feeLamports | number | Network fee for the transaction, in lamports |
feeUsdAmount | number | Network fee in USD |
feeMint | string | Mint address of the fee token |
feeTokenDecimals | number | Decimals of the fee token |
feeAmount | number | Fee amount in the fee token’s smallest unit |
totalTime | number | Time taken to craft the transaction, in milliseconds |
expireAt | string | Expiry timestamp for the crafted transaction |
code | number | Status code (0 for success) |
gasless | boolean | Whether the transaction is gasless |
Step 3: Sign and Execute
Sign the transaction from Step 2 with your wallet, then submit it along with the token details and metadata.| Field | Type | Required | Description |
|---|---|---|---|
transaction | string | Yes | Base64-encoded signed transaction from craft-txn |
requestId | string | Yes | requestId from the craft-txn response |
senderAddress | string | Yes | Solana wallet address of the sender |
tokenId | string | Yes | Token mint address to verify |
twitterHandle | string | Yes | Twitter/X handle of the token project |
description | string | Yes | Reason for the verification request |
senderTwitterHandle | string | No | Twitter/X handle of the submitter |
tokenMetadata | object | No | Token metadata to submit alongside verification. See Token Metadata Fields. |
paymentCurrency | string | No | Token symbol, not a mint address: JUP (default), SOL, USDC, or JUPUSD. Must match the currency used in craft-txn. |
paymentAmount | string | Conditional | Atomic input amount paid, from the craft response’s quotedInputAmount. Required when paymentCurrency is not JUP. |
jupOutputAmount | string | No | Atomic JUP output from the craft response (its amount field). Optional, but recommended on non-JUP paths so revenue tracks the JUP actually collected. |
| Field | Type | Description |
|---|---|---|
status | "Success" | "Failed" | Whether the transaction executed |
signature | string | On-chain transaction signature (present on success) |
error | string | Error message (present on failure) |
code | number | Error code (present on failure) |
totalTime | number | Time taken to execute, in milliseconds |
verificationCreated | boolean | Whether a verification request was created |
metadataCreated | boolean | Whether a metadata update request was created |
Pay with SOL, USDC, or JUPUSD
To pay with a non-JUP currency, setpaymentCurrency on both the craft and execute steps. The craft step returns an Ultra swap that converts your input token into JUP, sized with a small buffer so the swap yields at least 1000 JUP.
Request the transaction with your chosen currency:
| Field | Type | Description |
|---|---|---|
inputMint | string | Input token mint address |
inputDecimals | number | Input token decimals |
quotedInputAmount | string | Atomic input amount for the swap, sized to yield at least 1000 JUP |
maxInputAmount | string | Maximum atomic input amount for the swap. Equal to quotedInputAmount on the current swap flow. |
paymentAmount (required on non-JUP paths) and jupOutputAmount (optional, for revenue tracking). paymentAmount is the input amount from the craft response’s quotedInputAmount, and jupOutputAmount is the craft response’s amount:
Token Metadata Fields
ThetokenMetadata object in the execute request is optional. Include it to update metadata alongside your verification submission. Only tokenId is required, all other fields are optional.
| Field | Type | Description |
|---|---|---|
tokenId | string | Token mint address (required) |
name | string | Token display name |
symbol | string | Token ticker symbol |
icon | string | URL to token icon image |
website | string | Project website URL |
twitter | string | Twitter/X profile URL |
twitterCommunity | string | Twitter/X community URL |
telegram | string | Telegram group URL |
discord | string | Discord invite URL |
instagram | string | Instagram profile URL |
tiktok | string | TikTok profile URL |
tokenDescription | string | Short description of the token |
circulatingSupply | string | Circulating supply value |
useCirculatingSupply | boolean | Whether to use the provided circulatingSupply value |
circulatingSupplyUrl | string | URL to a live circulating supply endpoint |
useCirculatingSupplyUrl | boolean | Whether to use the provided circulatingSupplyUrl |
coingeckoCoinId | string | CoinGecko coin ID for price data |
useCoingeckoCoinId | boolean | Whether to use the provided coingeckoCoinId |
otherUrl | string | Any other relevant URL |
Known Projects and Launchpads
If you are a known project or launchpad on Solana, DM @jup_vrfd from your organization account on X. This links your Developer Platform OrgId to your submissions, which helps the VRFD team review them.API Reference
Check Eligibility
Check if a token can be verified
Craft Transaction
Get an unsigned 1000 JUP payment transaction
Execute
Submit signed transaction with token details
