Skip to content

Logo

Cash Bulls

Supports in this guide: Payments

Provider website: cashbulls.io


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

  1. Choose account type
  2. Get your credentials (from Cash Bulls)
  3. Connect in Dashboard
  4. Send an API request

Choose account type

Cash Bulls can be connected in different ways (depending on your needs):

  • If you do H2H card payments (card data sent directly) -> choose H2H Merchant account
  • If you do redirect payments (customer redirected to a hosted payment page, covers local payment methods, card p2p, Apple Pay and Google Pay) -> choose Provider account

If you are not sure which one to use, confirm with your Corefy account manager.


Prerequisites: get from Cash Bulls

Get the following values for your Cash Bulls project/account:

  • API Key -> Corefy field api_key -> example: cb_live_51HxJ2kQmP -> where to find: Cash Bulls backoffice / issued by Cash Bulls manager
  • Secret Key -> Corefy field secret_key -> example: sk_9fT3q7mXeR2d -> where to find: Cash Bulls backoffice / issued by Cash Bulls manager

Both the H2H Merchant account and the Provider account use this same pair of credentials - each account type is still connected separately in the Dashboard.


Payments processing (connect H2H Merchant account, create payment-invoice)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

Open Cash Bulls in the provider directory and press Connect at Cash Bulls Provider Overview page in the New connection section. Choose H2H Merchant account.

Step 2 - Fill in fields and select settings

  • API Key -> api_key
  • Secret Key -> secret_key
  • API URL -> api_url (optional, overrides the default Cash Bulls API endpoint)

Choose Currency and Features. You can set these parameters according to available currencies and features for your Cash Bulls account, but it is necessary to check details of the connection with your Corefy account manager.

Success

You have connected Cash Bulls H2H Merchant account!


First request to Corefy API (MIN)

What it does: creates a payment-invoice.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "d78119d7-ee20-49a0-aeea-4d857c6c1899",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "c29e3d9f-1a3d-4ae7-8b25-5fcd272fc8d3",
        "email": "johnsmith@gmail.com",
        "phone": "+380991234567"
      }
    }
  }
}
Cash Bulls requires the customer's email and phone on every H2H sale request - a request missing either one is rejected before it reaches Cash Bulls.

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "06fa1ea9-8a5b-4dbc-b67b-6236b3b9af3d",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10.04,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+380991234567",
        "address": {
          "city": "Odessa",
          "country": "UA",
          "full_address": "Pushkina 1",
          "post_code": "65001",
          "region": "Odessa"
        }
      }
    }
  }
}
Cash Bulls H2H Merchant account supports USD, EUR, AZN and RUB - the service code follows the payment_card_<currency>_hpp pattern (e.g. payment_card_usd_hpp, payment_card_azn_hpp).


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


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

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

Open Cash Bulls in the provider directory and press Connect at Cash Bulls Provider Overview page in the New connection section. Choose Provider account.

Step 2 - Fill in fields and select settings

  • API Key -> api_key
  • Secret Key -> secret_key
  • API URL -> api_url (optional, overrides the default Cash Bulls API endpoint)
  • Test Mode -> (enable if you are using sandbox credentials)

Choose Currency and Features. You can set these parameters according to available currencies and features for your Cash Bulls account, but it is necessary to check details of the connection with your Corefy account manager.

Success

You have connected Cash Bulls Provider account!


First request to Corefy API

What it does: creates a payment-invoice.

Payment - Actual

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8afec793-9b41-4dc4-b281-c76cc54ffb89",
      "service": "payment_card_kzt_hpp",
      "currency": "KZT",
      "amount": 1000,
      "customer": {
        "reference_id": "cus_456",
        "metadata": {
          "ip": "203.0.113.42"
        }
      }
    }
  }
}
customer.metadata.ip is required on every Provider account request, regardless of payment method - a request without it is rejected before it reaches Cash Bulls.

Cash Bulls Provider account is a multi-method connector - besides card payments (p2p, shown above for KZT, also available for AZN as payment_card_azn_hpp), it supports several local payment methods and digital wallets, each via its own service code:

  • sepa_transfer_eur_hpp - SEPA transfer, EUR
  • upi_inr_hpp - UPI, INR
  • blik_pln_hpp - BLIK, PLN
  • applepay_eur_hpp - Apple Pay, EUR
  • googlepay_eur_hpp - Google Pay, EUR

All of these additionally require the customer's name, phone and email in the request. SEPA transfer and BLIK further require the customer's full address (city, region, full_address, post_code, country); UPI additionally requires fields.account with the payer's UPI ID.


Extended request

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


Additional info

  1. Cash Bulls sends a per-transaction callback URL (webhook_url) together with every Provider account payment request - Corefy generates and handles this automatically, there is no separate webhook URL to configure in the Cash Bulls back office.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify you used the correct keys for the chosen environment (sandbox vs production)
  • Currency or service is not supported -> confirm allowed currencies/features in your Cash Bulls account and in Corefy
  • Missing required fields -> SEPA transfer, BLIK and UPI require the customer's name, phone, email (and address for SEPA/BLIK, a UPI account for UPI) - card payments and H2H sales still require email and phone; provide the missing fields in the API request
  • Not sure which account type to use? -> ask your Corefy account manager

Question

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