Skip to main content
payram-auth Authenticate with a PayRam instance to access merchant dashboard APIs. Covers login with email/password, JWT Bearer token usage, automatic token refresh, and extracting tokens from a browser session. Use when connecting to PayRam APIs, troubleshooting authentication, or building integrations that need merchant-level access to payment data, analytics, and sweep management.
Ir para a instalação Skills Marketplace Descubra e explore skills de IA criadas pela comunidade.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Mostrar detalhes do prompt Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
npx skills add https://github.com/PayRam/payram-mcp --skill payram-authO comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.
Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.
Baixar Zip Baixando... Mais deste repositório Set up and operate PayRam - a private, self-hosted crypto payment gateway (payment links, hosted checkout, USDC/BTC/ETH deposits, sweeps to a cold wallet you control). No signup, no KYB. Use this skill when a user wants to accept crypto payments, set up a payment gateway, create payment links, or integrate PayRam into an application.
payram-checkout-integration Integrate PayRam checkout flow into web applications. Generate payment links, embed payment pages, handle redirects, and process payment confirmations. Supports Express, Next.js, FastAPI, Laravel, Gin, Spring Boot. Use when adding crypto checkout to e-commerce, building payment forms, implementing deposit flows, or creating hosted payment pages for crypto acceptance.
The end-to-end map for an agent standing up PayRam and taking it live — install (merchant OR operator), deposit wallets, gas + sweep operations, app integration, and testing. Routes every stage to the right tool or skill and covers both install roles. Use this FIRST when asked to "set up PayRam", "get PayRam ready to take payments", "which PayRam tool/skill do I use for X", or when planning a full deployment.
Ocupações relacionadas SOC
Baseado na classificação ocupacional SOC
name payram-auth description Authenticate with a PayRam instance to access merchant dashboard APIs. Covers login with email/password, JWT Bearer token usage, automatic token refresh, and extracting tokens from a browser session. Use when connecting to PayRam APIs, troubleshooting authentication, or building integrations that need merchant-level access to payment data, analytics, and sweep management.
PayRam Authentication
First time with PayRam? See payram-setup
PayRam uses JWT Bearer tokens for dashboard/merchant API access and API keys for external platform integrations. This skill covers the JWT flow — the one you need for querying payments, analytics, sweeps, and all dashboard data.
When to Use
Authenticate before calling any PayRam dashboard API
Refresh an expired access token without re-entering credentials
Extract tokens from a browser session for agent use
Troubleshoot 401/403 errors on PayRam API calls
Quick Reference
Item Value Access token lifetime 15 minutes (900 seconds) Refresh token lifetime 7 days Refresh sliding window New refresh token issued when < 48 hours remain Auth header Authorization: Bearer <accessToken>Algorithm HS256 (HMAC-SHA256)
Option A: Login with Email & Password
If you have the merchant's email and password, call the signin endpoint directly.
Request POST {BASE_URL}/api/v1/signin
Content-Type: application/json
{
"email": "merchant@example.com",
"password": "YourPassword123!"
}
Response (200 OK) {
"accessToken" : "eyJhbGciOiJIUzI1NiIs..." ,
"refreshToken" : "eyJhbGciOiJIUzI1NiIs..." ,
"expiresIn" : 900 ,
"tokenType" : "Bearer" ,
"member" : {
"id" : 1 ,
"email" : "merchant@example.com" ,
"name" : "Merchant Name" ,
"memberType" : "internal"
} ,
"role" : {
"name" : "root" ,
"displayName" : "Root Administrator"
} ,
"resetPasswordRequired" : false }
Error Responses Status Meaning What to do 400 Malformed JSON Check request body format 401 Wrong email or password Verify credentials
Example (curl) curl -s -X POST "${BASE_URL} /api/v1/signin" \
-H "Content-Type: application/json" \
-d '{"email":"merchant@example.com","password":"YourPassword123!"}' \
| jq '{accessToken, refreshToken, expiresIn}'
Option B: Extract Tokens from Browser If you're already logged into the PayRam dashboard in a browser, you can grab the tokens without re-entering credentials.
Steps
Open the PayRam dashboard in your browser
Open DevTools (F12 or Cmd+Shift+I)
Go to Application tab (Chrome) or Storage tab (Firefox)
Look in Local Storage or Cookies for your PayRam domain
Copy the accessToken and refreshToken values
Alternatively, from the Network tab:
Refresh the page
Click any API request to your PayRam server
Look at the Authorization: Bearer ... header — that's your access token
Tip : The access token expires in 15 minutes. Always grab the refresh token too so the agent can auto-renew.
Token Refresh Access tokens expire every 15 minutes. Use the refresh token to get a new one — no password needed.
Request POST {BASE_URL}/api/v1/refresh
Content-Type: application/json
{
"refreshToken": "eyJhbGciOiJIUzI1NiIs..."
}
Response (201 Created) {
"accessToken" : "eyJhbGciOiJIUzI1NiIs...(new)..." ,
"refreshToken" : "eyJhbGciOiJIUzI1NiIs...(may be new)..." ,
"expiresIn" : 900 ,
"tokenType" : "Bearer"
}
Sliding Window Behavior
If the refresh token has more than 48 hours remaining: same refresh token is returned, only the access token is new.
If the refresh token has less than 48 hours remaining: a new refresh token is also returned, and the old one is revoked.
Important : Always store the refresh token from the response — it may be different from the one you sent.
Example (curl) curl -s -X POST "${BASE_URL} /api/v1/refresh" \
-H "Content-Type: application/json" \
-d "{\"refreshToken\":\"${REFRESH_TOKEN} \"}" \
| jq '{accessToken, refreshToken, expiresIn}'
Using the Access Token Once you have an access token, include it in every API request:
Authorization: Bearer eyJhbGciOiJIUzI1NiIs...
Discovering Your Project ID Most PayRam data APIs require a PROJECT_ID (external platform ID). You do not need to ask the user for this — discover it automatically:
GET {BASE_URL}/api/v1/external-platform/details
Authorization: Bearer <ACCESS_TOKEN>
[
{
"id" : 1 ,
"name" : "My Store" ,
"referenceId" : "ref_abc" ,
"createdAt" : "2025-01-15T10:00:00Z"
}
]
Use the id from the first platform (most merchants have one). If multiple platforms exist, pick the one matching the user's context or list them and ask.
Example: Call Payment Summary curl -s -X POST "${BASE_URL} /api/v1/external-platform/${PROJECT_ID} /payment/summary" \
-H "Authorization: Bearer ${ACCESS_TOKEN} " \
-H "Content-Type: application/json" \
-d '{}'
Auto-Refresh Pattern for Agents When building an agent that calls PayRam APIs, use this pattern:
Try the API call with the current access tokenIf 401 is returned : call /api/v1/refresh with the refresh tokenStore the new tokens (both access AND refresh — refresh may change)Retry the original API call with the new access tokenIf refresh also fails (401) : the refresh token has expired — ask the user to log in again or provide a new token from the browser
Pseudocode function callPayramAPI(method, url, body):
response = httpRequest(method, url, body, headers: {Authorization: Bearer ACCESS_TOKEN})
if response.status == 401:
refreshResponse = POST /api/v1/refresh {refreshToken: REFRESH_TOKEN}
if refreshResponse.status == 201:
ACCESS_TOKEN = refreshResponse.accessToken
REFRESH_TOKEN = refreshResponse.refreshToken // may be new!
return httpRequest(method, url, body, headers: {Authorization: Bearer ACCESS_TOKEN})
else:
raise "Session expired — please provide a new token"
return response
JWT Token Structure
Access Token Claims {
"mid" : 1 ,
"email" : "merchant@example.com" ,
"roles" : [ "root" ] ,
"perms" : [ "read_payment_request" , "read_analytics" , "..." ] ,
"typ" : "access" ,
"exp" : 1711009500 ,
"iss" : "payram-core"
}
Refresh Token Claims {
"mid" : 1 ,
"typ" : "refresh" ,
"jti" : "1-1711008600000000000" ,
"exp" : 1711613400 ,
"iss" : "payram-core"
}
JWT vs API Key — When to Use Which JWT Bearer Token API Key Header Authorization: Bearer <token>API-Key: <key>Who uses it Merchants (dashboard users) External platforms (integrations) Lifetime 15 min access + 7 day refresh Permanent until revoked Scope Full dashboard access (based on role) Scoped to specific platform + permissions Use for Analytics, payments, sweeps, settings Creating payments, webhooks, SDK calls
For querying dashboard data (payments, volume, sweeps, analytics) — use JWT Bearer tokens.
Logout
Single Session POST {BASE_URL}/api/v1/logout
Authorization: Bearer <accessToken>
Content-Type: application/json
{"refreshToken": "eyJ..."}
All Sessions POST {BASE_URL}/api/v1/logout-all
Authorization: Bearer <accessToken>
Troubleshooting Error Cause Fix 401 on API call Access token expired Refresh using /api/v1/refresh 401 on refresh Refresh token expired or revoked Login again or get new token from browser 403 Insufficient permissions User role lacks required permission Check role assignments in dashboard resetPasswordRequired: truePassword reset forced by admin Call change-password endpoint first
Related Skills 