Skip to content

Logo

BuziPay

Supports in this guide: Payments

Provider website: buzipay.com


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

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

Choose account type

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

  • If you do H2H card payments -> choose H2H Merchant account

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


Prerequisites: get from BuziPay

Get the following values for your BuziPay project/account:

  • Secret key -> Corefy field secret_key -> example: sk_live_9f8e7d6c5b4a3210 -> where to find: BuziPay backoffice / issued by BuziPay manager. Used to authorize every API request to BuziPay.
  • Webhook secret key -> Corefy field webhook_secret_key -> example: whc_1a2b3c4d5e6f7a8b -> where to find: BuziPay backoffice (issued when you register the webhook endpoint, see Additional info) / issued by BuziPay manager. Used to verify the signature of callbacks BuziPay sends to Corefy.
  • API URL (optional) -> Corefy field api_url -> example: https://api.buzipay.com -> where to find: BuziPay backoffice / issued by BuziPay manager. Fill it in only if BuziPay gave you a dedicated API address; when empty, Corefy uses the standard BuziPay production or sandbox URL, depending on Test mode.

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

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • Secret key -> (key for authorizing requests to BuziPay)
  • Webhook secret key -> (key for verifying BuziPay callback signatures)
  • API URL -> (optional, overrides the default BuziPay API address)
  • Test mode -> (enable if you are using sandbox credentials)

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

Success

You have connected BuziPay 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": "8afec793-9b41-4dc4-b281-c76cc54ffb89",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 100
    }
  }
}

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": 100,
      "description": "Order #1234",
      "customer": {
        "reference_id": "bc75bc54-5023-4f98-8c0d-ec5ed7e8f380",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "address": {
          "country": "DE",
          "region": "Berlin",
          "city": "Berlin",
          "post_code": "10115",
          "full_address": "1st Street 1"
        }
      }
    }
  }
}
All customer fields are optional. When present, they are sent to BuziPay as the cardholder's billing details. If address.full_address is not provided, address.street is used instead. description is optional too; if it is empty, Corefy sends the payment's own identifier as the description. BuziPay also supports KZT (service code payment_card_kzt_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

Additional info

  1. For callbacks processing you need to register the webhook endpoint in the BuziPay backoffice.

    • For H2H Payments endpoint is /buzipay/callback

    After registering the endpoint, BuziPay issues a Webhook secret key. Enter it in the connection settings: Corefy uses it to verify the signature of each callback.

  2. BuziPay supports 3D Secure. When the card requires authentication, the customer is redirected to the 3D Secure page and the final status is received after they complete it.

  3. Refunds are supported, including partial refunds. Only one refund can be made per payment.


FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify you used the correct Secret key for the chosen environment (sandbox vs production) and that Test mode matches it
  • Callbacks are not processed -> check that the callback URL is set in the BuziPay backoffice and that the Webhook secret key in Corefy matches the one in BuziPay
  • Currency not supported -> confirm allowed currencies/features in your BuziPay account and in Corefy
  • Not sure which account type to use? -> ask your Corefy account manager

Question

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