Skip to main content
You can use the mock UI on the staging dashboard to execute test transactions with a few clicks. The staging environment also includes mock API endpoints for more flexibility. Use them to test your integration end-to-end without moving real funds.

​
Mock endpoints

​
Mock Deposit

Simulates a crypto deposit to a user’s account. Use this to test webhook delivery for Deposit events and to fund test accounts for subsequent operations. 
curl --request POST \
  --url https://staging-api.getpartna.com/v4/mock/deposit \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --header 'x-api-user: YOUR_USERNAME' \
  --data '{
    "amount": 100,
    "currency": "USDT"
  }'
See the full reference: Mock Deposit

​
Mock Fiat Deposit

Simulates a fiat (local currency) deposit. Use this to test the collect flow and onramp scenarios where a user pays in fiat. 
curl --request POST \
  --url https://staging-api.getpartna.com/v4/mock/fiat-deposit \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY' \
  --header 'x-api-user: YOUR_USERNAME' \
  --data '{
    "amount": 50000,
    "currency": "NGN"
  }'
See the full reference: Mock Fiat Deposit You can also run these from the staging dashboard UI: Mock Deposits.

​
Testing workflow

A typical testing workflow looks like this:
1

Create a test user account

Use Create Account to set up a test user. In staging, KYC can be completed with test data.
2

Complete KYC

Run through the KYC flow using test identity data. In staging, verification succeeds with any valid-format input.
3

Fetch a rate

Call Get Rate to get a conversion rate and rate key.
4

Initiate a ramp request

Use Onramp and Offramp to create a test transaction.
5

Simulate the payment

For onramp: call Mock Fiat Deposit to simulate the user’s local currency payment. For offramp: call Mock Deposit to simulate an incoming crypto payment.
6

Verify webhook delivery

Confirm your webhook endpoint received the expected events (Deposit, Convert, Transfer, etc.) with valid signatures.

​
Webhook testing tips

If you do not have a publicly accessible server during development, use a tunneling tool like ngrok or webhook.site to expose your local endpoint: 
ngrok http 3000
Then set your webhook URL to the forwarding address (e.g., https://abc123.ngrok.io/webhook) via the Update Webhook URL endpoint. If you just want to inspect payloads without writing code, webhook.site gives you a unique URL that logs every request it receives.

​
Going to production

When your staging integration is working correctly:
  1. Swap the base URL from https://staging-api.getpartna.com/v4 to https://api.getpartna.com/v4
  2. Replace staging credentials with your production x-api-key and x-api-user
  3. Update your webhook signature verification to use the production public key
  4. Update your webhook URL to your production endpoint
No other code changes are required. The API behaves identically in both environments.