Qostiq (Kvitum)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Shop ID
• Secret Key
• Project ID (optional)
• Aggregator
• API URL (optional)
• Test Mode -> (enable if you are using sandbox credentials)

Choose Currency and Features. UAH, USD, EUR, and KZT are confirmed; 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; card data itself is collected and submitted separately by Corefy's checkout/SDK layer, not as part of this request.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8e3dbbb0-17af-4c9a-bedb-93bdac6900a2",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com"
      }
    }
  }
}

customer is optional - the only Constant on this flow is EMAIL, so anything else you don't send is simply left out. For UAH specifically, customer.reference_id is forwarded to Qostiq as a customer identifier (falls back to a generated one if omitted).

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

Options are configured on the Corefy side and affect how Corefy builds provider requests or processes responses.

Currently available options (3)

• ignore_callback - tells Corefy to disregard Qostiq's own callback notifications entirely.
• send_email - forwards the customer's email to Qostiq.
• forced_rejection_delay - delays automatic rejection of a stalled transaction by the given number of seconds.

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.

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 -> only used at all if the send_email option above is enabled.

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Merchant ID
• Secret Key
• Project ID (optional)
• Aggregator
• API Type (optional) -> Fiat or Crypto
• API URL (optional)
• Test Mode -> (enable if you are using sandbox credentials)

Choose Currency / Features - the Qostiq wallet, bank transfer, and Kazakhstan mobile operator top-ups are each available for different currencies - see Additional info for the full list.

First request to Corefy API (MIN)

What it does: creates a payment-invoice and returns a redirect link to Qostiq's hosted payment page.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8e3dbbb0-17af-4c9a-bedb-93bdac6900a2",
      "service": "kvitum_usd_hpp",
      "currency": "USD",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "kvitum_usd_hpp",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123"
      }
    }
  }
}

customer is optional for the Qostiq wallet and bank transfer methods. For the Kazakhstan mobile operator methods (activ_kcell_kzt_hpp/altel_tele2_kzt_hpp/beeline_kzt_hpp) you also need fields.phone - see Additional info for the full method list, and the dont_send_phone option below if you'd rather not forward it.

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

Options are configured on the Corefy side and affect how Corefy builds provider requests or processes responses.

Currently available options (2, by service)

• checkout_lifetime / checkout_language - on the Qostiq wallet services (kvitum_<ccy>_hpp) only.
• dont_send_phone - on the Kazakhstan mobile operator services (activ_kcell_kzt_hpp/altel_tele2_kzt_hpp/beeline_kzt_hpp) only.

Connect Provider account in Corefy Dashboard

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

First request to Corefy API (MIN)

What it does: creates a payout-invoice and sends funds to a Qostiq wallet, a card, or a Kazakhstan mobile operator account.

Payout - MIN (Qostiq wallet)

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "0dde9e79-2c64-4703-adaf-93d710633401",
      "service": "kvitum_usd",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123"
      },
      "fields": {
        "account_id": "qostiq-wallet-id-123"
      }
    }
  }
}

Payout - MAX (card, EUR)

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "7976b4ce-fadd-4585-baa0-6b02c65351dc",
      "service": "payment_card_eur",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith"
      },
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

fields.account_id (Qostiq wallet payouts) or fields.card_number (card payouts) is required depending on the method. For payment_card_eur specifically, the cardholder's first/last name is also required - taken from customer.name if present, otherwise from the CUSTOMER_FIRST_NAME/CUSTOMER_LAST_NAME constants below. This connector also supports Kazakhstan mobile operator payouts (activ_kcell_kzt/altel_tele2_kzt/beeline_kzt - use fields.phone_number).

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

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. Available only for the payment_card_eur payout service.

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)

• CUSTOMER_FIRST_NAME -> customer.name (first part)
• CUSTOMER_LAST_NAME -> customer.name (second part)