Skip to content

CoinsPaid

CoinsPaid

Supports in this guide: Payments, Payouts

Provider website: coinspaid.com

Note

CoinsPaid's merchant API and dashboard are branded "CryptoProcessing" - you sign in and manage your account at app.cryptoprocessing.com, not on the main coinspaid.com site.

What you need to do for start processing transactions (brief summary)

  1. Get your credentials (from CoinsPaid)
  2. Connect in Dashboard
  3. Send an API request

Prerequisites: get from CoinsPaid

Contact your CoinsPaid account manager to activate an API key and receive the following credentials.

  • Public key -> Corefy field public_key -> your activated API Key.
  • Secret key -> Corefy field secret_key -> shown only once when the key is created - save it, CoinsPaid will not show it again.
  • API URL -> Corefy field api_url -> optional; leave blank to use the standard production/sandbox endpoint matching your Test Mode setting.

Important

If you require IP whitelisting, ask your CoinsPaid account manager to whitelist Corefy's IP addresses.

BTC, BCH, ETH, LTC, XRP, USDT (ERC20/TRC20), USDC (multiple networks), and fiat-denominated crypto payments in UAH/USD/EUR.

Payments processing (connect Provider account, create payment-invoice)

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

Open CoinsPaid in the provider directory and press Connect at CoinsPaid Provider Overview page in the New connection section.

Step 2 - Fill in fields and select settings

  • Public key
  • Secret key
  • API URL -> optional
  • Test Mode -> (enable if you are using sandbox credentials)
  • Currency / Features -> choose values available for your account

Success

You have connected CoinsPaid Provider account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice and redirects the customer to CoinsPaid's hosted checkout.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "e3bd5e0e-6b3e-4a5e-8e6e-9f7a5a2c6d1e",
      "service": "bitcoin_eur_hpp",
      "currency": "EUR",
      "amount": 50
    }
  }
}

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "a6c7d8e9-1f2a-4b3c-9d4e-5f6a7b8c9d0e",
      "service": "bitcoin_eur_hpp",
      "currency": "EUR",
      "amount": 50,
      "customer": {
        "reference_id": "cus_123",
        "email": "name@example.com",
        "description": "Order #1024"
      }
    }
  }
}

Important

customer is entirely optional for this connector - CoinsPaid's checkout page does not collect any customer details itself, so Corefy only forwards email, reference_id and description if you provide them; nothing is faked when they're missing.

Extended request (MAX)

Why add extra fields (typical reasons): - Provide additional customer details for compliance/reconciliation - Positively influence conversion rate - Include optional fields required by your specific flow

Options

Options are configured on the Corefy side and affect how Corefy builds provider requests or processes responses.

Currently available options (3)

  • title_key - picks which field from your own request metadata is sent to CoinsPaid as the payment's title/description shown on the checkout page.
  • payment_title_type - controls whether a partially paid crypto transaction is accepted or rejected.
  • timer - shows a countdown timer on CoinsPaid's checkout page (only applies to the coinspaid service, CoinsPaid's own balance-based method).
title_key

What it does: selects a key from the payment's metadata object whose value is sent to CoinsPaid as the transaction title. If not set, or the key isn't present in metadata, Corefy sends a generic Payment <payment number> title instead. Default: not set.

payment_title_type

What it does: Full Only requires the customer to send the exact amount or the payment is rejected; Partial Allowed lets Corefy accept a lower amount than requested. Default: not set (CoinsPaid's own account default applies). Allowed values: Full Only, Partial Allowed

timer

What it does: when enabled (and only for the coinspaid service), shows a countdown timer on the hosted checkout page. Default: false

Refunds

CoinsPaid does not support refunds.

Payouts processing (connect Provider account, create payout-invoice)

Connect Provider account in Corefy Dashboard

Uses the same Provider account connected above - no separate connection step.

First request to Corefy API (MIN)

What it does: creates a payout-invoice, sending crypto or crypto-denominated fiat funds to the customer.

Payout - MIN

POST /api/payout-invoices 

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "f1a2b3c4-5d6e-4f7a-8b9c-0d1e2f3a4b5c",
      "service": "bitcoin_eur",
      "currency": "EUR",
      "amount": 50,
      "customer": {
        "reference_id": "cus_456"
      }
    }
  }
}

Important

CoinsPaid's payout methods pay out to a pre-arranged wallet/account on CoinsPaid's own side rather than to recipient details you supply per request - there are no fields for recipient wallet addresses in this connector's request format.

Extended request (MAX)

Why add extra fields (typical reasons): - Provide additional customer details for compliance/reconciliation - Positively influence conversion rate - Include optional fields required by your specific flow

Refunds

CoinsPaid does not support refunds on Payouts.

Additional info

  1. Callback-only status updates on both flows - CoinsPaid notifies Corefy of status changes via asynchronous callback; there is no active status-polling available for either Payments or Payouts, so make sure your account's callback/IP settings are correctly configured.
  2. Callback signature verification is always enforced - every callback must carry a valid X-Processing-Signature header computed from your Secret key; a callback without it, or with a mismatched signature, is rejected outright.
  3. No recurring - this connector does not support saving/charging a token through Corefy.
  4. Service codes follow the pattern <coin>_<currency>_hpp for Payments and <coin>_<currency> for Payouts (for example ethereum_usd_hpp / ethereum_usd) - many coin/currency/network combinations are available (BTC, BCH, ETH, XRP, LTC, USDT on ERC20/TRC20, USDC on several networks, plus CoinsPaid's own balance-based coinspaid service); check your account's enabled currencies in the Dashboard for the exact list.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify the Public key and Secret key for the selected environment (Test Mode on/off)
  • Callback rejected / signature mismatch -> confirm the Secret key configured in Corefy matches the one currently active on your CoinsPaid account
  • Payment stuck pending with no status update -> this connector has no active status request; confirm your callback endpoint and any required IP whitelisting are correctly set up
  • Currency or service is not supported -> confirm the currency/coin is enabled on your CoinsPaid account's "Currencies Info" settings and in Corefy
  • Refund fails -> CoinsPaid does not support refunds through Corefy

Question

Still looking for help connecting your CoinsPaid account? Please contact our support team!