BitAndPay

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Merchant ID
• Merchant Site ID
• Merchant Token
• Live URL
• Test Mode -> (enable if you are using sandbox credentials)

Choose Currency / Features; check with your Corefy account manager which are enabled for your account.

First request to Corefy API (MIN)

What it does: creates a payment-invoice and redirects the customer to a BitAndPay-hosted page to complete the payment via Pay by Bank or BLIK, depending on what's enabled for your account.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "3a4b5c6d-7e8f-4a0b-8c12-3d4e5f6a7b8c",
      "service": "paybybank_eur_hpp",
      "currency": "EUR",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "4b5c6d7e-8f9a-4b1c-8d23-4e5f6a7b8c9d",
      "service": "paybybank_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "address": {
          "country": "DE",
          "region": "Bavaria",
          "city": "Munich",
          "full_address": "1 Main street",
          "post_code": "80331"
        }
      }
    }
  }
}

customer is entirely optional - everything is only used to prefill the hosted form, it never blocks the sale.

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

No Options are configured for this connector.

Constants (fallback fields)

Constants are static values that Corefy can send to the provider instead of dynamic data from your API request, when those fields are missing in the request. For BitAndPay, they only apply to the Pay by Bank method (paybybank_eur_hpp) - BLIK has no Constants.

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)

• email -> customer.email
• phone -> customer.phone
• first_name -> customer.name (first part)
• last_name -> customer.name (second part)
• country_code -> customer.address.country
• state -> customer.address.region
• city -> customer.address.city
• address -> customer.address.full_address
• post_code -> customer.address.post_code
• user_ip -> customer.metadata.ip

Refunds

This connector does not support refunds.