Skip to main content
This guide walks you through the complete process of becoming a Paycrest provider, from initial signup to running a production provision node. Follow these steps to start earning from on-ramp and off-ramp orders.

Step 1: Signup as a Provider

  1. Visit https://app.paycrest.io
  2. Sign up as a Provider
  3. Complete the registration process

Step 2: Initiate KYB Process

  • Complete the basic in-app Know-Your-Business (KYB) process
  • This process can run concurrently with PSP account setup
  • KYB approval is required to add your first node and to create or activate offers

Step 3: Register with Payment Service Providers (PSPs)

Your provision node can support multiple payment service providers to ensure reliable transaction processing. The PSPs available to you are listed on the PSPs page of your dashboard, so you can begin PSP account setup in parallel with your KYB process.

Obtain Required Credentials

You need two credential groups:
  1. Paycrest Aggregator Credentials (from your Paycrest dashboard)
    • Go to Settings → API Keys
    • Copy:
      • API Key -> set as AGGREGATOR_CLIENT_ID
      • API Secret -> set as AGGREGATOR_SECRET_KEY
  2. PSP Credentials (from each PSP portal)
    • For each PSP you enable, collect the required fields (for example: API key, client secret, client assertion, account ID, base URL, callback URL, webhook secret)
    • Use the PSPs page to see the exact environment variable keys to populate
    • Add these values to your node .env

Step 4: Provision Node Setup

Choose your provision node hosting method:

Option A: Blockops (Managed hosting)

  • Managed hosting with guided setup
  • Video setup guide available
  • Start here: https://blockops.network
  • After setup, obtain the Host Identifier URL from Blockops
  • In the app: Settings → Node → Add a node → Self hosted — paste the URL and click Save node URL
Choose this option if you want faster setup with minimal infrastructure management. A Paycrest provision node is a backend service hosted on Docker Hub. The deployment process involves pulling the Docker image, configuring environment variables, and starting the server. Requirements:
  • Docker installed on your server
  • Access to Docker Hub
  • Server with internet connectivity
  • Minimum 512MB RAM, 1 vCPU (tested on DigitalOcean $5 droplet)
Deployment Steps:
  1. Pull the Docker Image
  1. Create Environment Configuration Create a .env file with your configuration:
Credential Mapping
  • AGGREGATOR_CLIENT_ID must be your Paycrest API Key (Settings → API Keys)
  • AGGREGATOR_SECRET_KEY must be your Paycrest API Secret (Settings → API Keys)
  • PSP variables (<PSP>_*) use values issued by each PSP. Prefixes match PSPs listed in the dashboard; availability depends on your corridor and currency.

EVM_PRIVATE_KEY explained

  • What it is: The private key for a dedicated EVM wallet (EOA) used by your provision node.
  • When you need it: Required for EVM on-ramp-related wallet/authorization flows. If you’re running off-ramp-only operations, you can leave it unset.
  • How to generate it: Create a new dedicated EVM wallet (do not reuse a personal wallet) and use that wallet’s private key.
  • Security: Treat this as a production secret. Never commit it to git, store it in a secure secret manager or protected .env, and rotate it immediately if exposed.

Starknet on-ramp envs explained

  • What they are:
    • STARKNET_SNIP9_USER_ADDRESS — Starknet account address used to sign SNIP-9 OutsideExecution payin messages
    • STARKNET_SNIP9_PRIVATE_KEY — private key for that Starknet account
  • When you need them: Required when fulfilling Starknet on-ramp (payin) orders. If you only handle EVM or off-ramp-only flows, you can leave them unset.
  • Address format: Use a Starknet felt hex address (0x + 63–64 hex characters), not an EVM checksum address.
  • Security: Treat both as production secrets. Never commit them to git, store them in a secure secret manager or protected .env, and rotate them immediately if exposed.
Important Notes:
  • One node works for multiple currencies and can support multiple PSPs (for the same currency)
  • Only configure the variables for the PSPs you are using
  • If there is no comment on a credential key that has a value, DO NOT change that value
  • DO NOT change the value of AGGREGATOR_BASE_URL
  • The dashboard PSPs page shows the exact environment variable keys per PSP
  • Retrieve the credential values from each PSP and place them in your .env
  1. Start the Service
  1. Verify Deployment Check the info endpoint to confirm your node is running and reporting provider metadata:
Expected response:
  1. Configure Host Identifier
  • Take the base URL of your server (e.g., http://your-server-ip:8000)
  • In the app: Settings → Node → Add a node → Self hosted — paste the URL and click Save node URL
Benefits:
  • Complete control over infrastructure
  • Custom security configurations
  • No dependency on third-party services
  • Potential cost savings at scale

Step 5: Create Offers

In Offers, click Create offer for a currency. Each offer sets:
  • Side: Sell (off-ramp) or Buy (on-ramp). Buy offers use PSPs that support payins.
  • Token and Networks
  • Rate: floating (recommended; market rate plus a margin) or fixed. Local stablecoin corridors are fixed only.
  • Rate slippage: advised, to handle volatility
  • Fee bounds (optional): minimum and maximum flat fee in fiat
  • Order limits: minimum and maximum order size. Set the maximum based on the fiat balance in your PSP account.
  • PSPs: all PSPs configured on your node, or a subset
  • Settlement addresses: one per network family. For Starknet, use a Starknet address (0x + 63–64 hex characters), not an EVM address.
Protocol fee: A protocol fee, a percentage of each order, is deducted at settlement. It appears as transactionFee on provider orders in the API and as Protocol fee on order details in the dashboard.

Step 6: Test & Go Live

  • Turn on Accepting offers for the currency to start receiving orders
  • Check PSP balances in Balances and keep your PSP accounts funded
Test with Noblocks: Route an order to your node: https://noblocks.xyz?provider=YOUR_PROVIDER_ID (Replace YOUR_PROVIDER_ID with your actual provider ID)

Onboarding Checklist

Use this checklist to track your progress:

Technical Requirements

Infrastructure Requirements

Minimum Requirements:
  • 512MB RAM, 1 vCPU (tested on DigitalOcean $5 droplet)
  • 50GB+ storage
  • Stable internet connection
  • Docker installed (for self-hosted deployment)
Note: The minimum requirements are based on real-world testing. A DigitalOcean $5 droplet (512MB RAM, 1 vCPU, 50GB bandwidth) is sufficient for running a Provision Node in production.

Docker Installation (For Self-Hosted)

If you choose self-hosted deployment, install Docker on your server:

Security Best Practices

Network Security

  • Use firewalls to restrict access
  • Implement rate limiting
  • Enable DDoS protection
  • Use VPN for secure access

Key Management

  • Store API keys securely
  • Rotate keys regularly
  • Use environment variables
  • Implement key encryption

Monitoring and Alerting

  • Set up log aggregation
  • Configure performance alerts
  • Monitor transaction volumes
  • Track error rates

Troubleshooting

Common Issues

Node Not Starting
API Connection Issues
Database Connection Errors

Getting Help

When to Contact Support

Most providers can complete setup without support. Contact support only if:
  • KYB remains pending beyond expected review time
  • A required PSP is unavailable for your corridor
  • Node status remains offline after valid hostIdentifier and .env setup
  • API keys under Settings → Payout → API Keys are missing or cannot be copied/rotated

Next Steps

After successfully deploying your Provision Node:
  1. Test Transactions: Process test transactions to verify functionality
  2. Monitor Performance: Track your node’s performance and earnings
  3. Scale Up: Consider deploying additional nodes for increased capacity
  4. Optimize: Fine-tune pricing and configuration based on market conditions
For detailed API documentation and advanced configuration options, see the API Reference.