Betterbro

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Point ID
• Account ID
• Wallet ID
• API Key
• API URL (optional)
• Currency
• Test Mode -> (enable if you are using sandbox credentials)

First request to Corefy API (MIN)

What it does: creates a payment-invoice and redirects the customer to a Betterbro-hosted page to complete the payment. Available methods - Binance Pay, Open Banking, BLIK, bank transfer, Mercado Pago, Astropay, Naranja X, Banco Nacion - depend on what's enabled for your account.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "9c1d3e56-7f8a-4b0c-8d12-3e4f5a6b7c8d",
      "service": "binancepay_usd_hpp",
      "currency": "USD",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "0d2e4f67-8a9b-4c1d-8e23-4f5a6b7c8d9e",
      "service": "binancepay_usd_hpp",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567"
      },
      "metadata": {
        "product_name": "Order #123",
        "product_type": "Goods"
      }
    }
  }
}

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

• ignore_timeout -> optional, boolean - if an active status check finds the payment failed specifically due to a timeout at Betterbro's side, reports it as still pending instead of failed, since a timed-out transaction may still complete later.

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 Betterbro, they only apply to the Binance Pay method.

Currently available constants (constant -> Corefy API field)

• productName -> metadata.product_name -> defaults to Other if neither is set.
• productType -> metadata.product_type -> defaults to Payment if neither is set.

Refunds

This connector does not support refunds.

Connect Provider account in Corefy Dashboard

Uses the same Provider account connection as Payments above - one connection covers both directions, nothing extra to fill in for payouts specifically.

First request to Corefy API (MIN)

What it does: creates a payout-invoice and sends funds via Binance Pay or bank transfer, depending on what's enabled for your account. Required fields vary by method - the Dashboard shows the exact field list once a method is selected.

Payout - MIN

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "1e3f5a78-9b0c-4d2e-8f34-5a6b7c8d9e0f",
      "service": "binancepay_usd",
      "currency": "USD",
      "amount": 10
    }
  }
}

Payout - MAX

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "2f4a6b89-0c1d-4e3f-8a45-6b7c8d9e0f1a",
      "service": "binancepay_usd",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123"
      }
    }
  }
}

customer is entirely optional.

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

• locale -> optional, enum (en, ua, ru, pt, fr, es) - configured on the binancepay_usd payout service - language used for any Betterbro-side notifications for this payout; defaults to en if not set.