Skip to content

Logo

Bitpace

Unlock the Future of Payments. What if you could tap into the power of over 600+ million crypto users worldwide? We can make it happen.

Supports in this guide: Payments

Provider website: bitpace.com

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

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

Prerequisites: get from Bitpace

Send a connection request at bitpace.com/get-started or contact your Bitpace manager directly to get your account verified and receive the following credentials.

  • Merchant code -> Corefy field merchant_code.
  • Password -> Corefy field password.
  • Callback secret key -> Corefy field callback_secret_key -> required for Corefy to verify the signature of Bitpace's callbacks; without it, incoming callbacks fail signature verification.

Available cryptocurrencies are auto-discovered live from your Bitpace account.

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

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • Merchant code
  • Password
  • Callback secret key
  • Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected Bitpace Provider account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice and redirects the customer to Bitpace's hosted checkout, where the actual cryptocurrency and deposit address are presented.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "5b138161-f2fa-4f38-9a20-350bb2530fb7",
      "service": "payment_card_crypto_eur_hpp",
      "currency": "EUR",
      "amount": 17,
      "customer": {
        "reference_id": "fa4a16b9-fc12-4a4b-9bcf-688ea6cd9cc5",
        "email": "test@test.com",
        "metadata": {
          "ip": "3.127.19.65"
        }
      }
    }
  }
}

Important

  • customer.email and customer.metadata.ip are both required - the payment request is rejected before reaching Bitpace if either is missing.
  • No Constants are configured for this connector - if a customer field is missing, it's simply not sent.

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "b0009a17-2831-4145-a890-e147e80d998e",
      "service": "payment_card_crypto_eur_hpp",
      "currency": "EUR",
      "amount": 15,
      "customer": {
        "reference_id": "fa4a16b9-fc12-4a4b-9bcf-688ea6cd9cc5",
        "name": "John Doe",
        "email": "test@test.com",
        "metadata": {
          "ip": "3.127.19.65"
        }
      }
    }
  }
}

customer.name is split into first/last name parts before being sent to Bitpace.

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

Bitpace does not support refunds.

Additional info

  1. Active reconciliation is available - an active status request can be used in addition to the asynchronous callback to finalize the payment.
  2. No recurring - this connector does not support saving/charging a token through Corefy.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify Merchant code and Password for the selected environment (test_mode)
  • Callback signature mismatch -> verify callback_secret_key is set correctly
  • Payment rejected before reaching Bitpace -> make sure customer.email and customer.metadata.ip are both present in the request
  • Currency or cryptocurrency is not supported -> confirm allowed currencies/features in your Bitpace account and in Corefy

Question

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