Paybis

Buy crypto with a card or bank transfer through a Paybis-hosted checkout.

Supports in this guide: Payments

Provider website: paybis.com

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

Get your credentials (from Paybis)
Connect in Dashboard
Send an API request

Prerequisites: get from Paybis

Contact your Paybis account manager to get your account verified and receive the following credentials.

Merchant email -> Corefy field merchant_email.
API key -> Corefy field api_key.
Webhook public key -> Corefy field webhook_public_key -> used to verify the signature of Paybis's callback.
Merchant private key -> Corefy field merchant_private_key -> optional, a file; if provided, Corefy signs every outgoing request to Paybis with it.
Payment method -> Corefy field payment_method -> optional, defaults to samegrid-credit-card if left blank.

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

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

Merchant email
API key
Webhook public key
Merchant private key (optional)
Payment method (optional)
Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected Paybis Provider account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice and redirects the customer to a Paybis-hosted checkout page where they buy the requested cryptocurrency with a card or bank transfer.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6be05631-8710-4b14-a369-1928a2b70eda",
      "service": "paybis_bitcoin_usd_hpp",
      "currency": "USD",
      "amount": 100,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com"
      }
    }
  }
}

Important

customer.reference_id and customer.email are required - missing either one causes a validation error, there is no fallback placeholder value sent in their place.
fields.blockchain_address (the destination wallet) is required to complete a purchase - it can be supplied in the request or sourced from a Dashboard Constant (see Constants below).

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "06fa1ea9-8a5b-4dbc-b67b-6236b3b9af3d",
      "service": "paybis_bitcoin_usd_hpp",
      "currency": "USD",
      "amount": 100,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com"
      },
      "fields": {
        "blockchain_address": "1Lbcfr7sAHTD9CgdQo3HTMTkV8LK4ZnX71"
      }
    }
  }
}

Extended request (MAX)

Why add extra fields (typical reasons): - Pre-fill the destination wallet instead of relying on a Constant - Include optional fields required by your specific flow

Constants (fallback fields)

Constants are static values that Corefy can send to Paybis instead of dynamic data from your API request, when those fields are missing in the request.

Priority (predictable rule): 1. If a value is present in the request -> Corefy uses the request value 2. Else if the constant is set -> Corefy uses the constant 3. Else -> provider may reject the request or apply its defaults (depends on provider)

Currently available constants (constant -> Corefy API field)

BLOCKCHAIN_ADDRESS -> fields.blockchain_address -> optional fallback for the destination wallet.

Two further Constants are configured per service on the Dashboard (not sent from your API request) and are both required for every service you enable:

Fee type -> whether the quoted price is internal or external.
Direction change -> whether the conversion direction is from or to the requested currency.

Refunds

Paybis does not support refunds.

Additional info

Request signing is optional - if you provide a Merchant private key, Corefy signs every outgoing request to Paybis with it; without one, requests are sent unsigned.
Webhook signature is always verified - Paybis signs every callback, and Corefy verifies it against your Webhook public key; a callback with an invalid signature is rejected.
No recurring - this connector does not support saving/charging a token through Corefy.
No active reconciliation - payment status is confirmed only via Paybis's asynchronous callback; there is no active status request for this connector.
Service naming - services follow the pattern paybis_{crypto}_{currency}_hpp (e.g. paybis_tether_eur_hpp), covering a wide range of cryptocurrencies settled in USD or EUR.

FAQ / Troubleshooting

Invalid credentials / auth error -> verify the merchant email and API key, and that Test Mode matches the credential environment
Currency or service is not supported -> confirm allowed crypto/currency combinations in your Paybis account and in Corefy
Payment fails validation -> customer.reference_id and customer.email are required; make sure both are sent
Destination wallet missing -> provide fields.blockchain_address in the request or set the BLOCKCHAIN_ADDRESS constant
Callback not accepted -> confirm the configured Webhook public key matches the one issued by Paybis
Refund fails -> Paybis does not support refunds through Corefy

Question

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