Constant Payments

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Shop ID
• Secret key
• Public key
• Test Mode -> (enable if you are using sandbox credentials)
• Provider URL -> leave at the default Constant Payments value
• 3DS mode -> leave at the default simple value
• Currency / Features -> choose values available for your account (RUB, EUR, USD, KZT, UAH, INR)

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": "6be05631-8710-4b14-a369-1928a2b70eda",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "c22e66d5-48fa-41b0-b322-55a985204e50",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "name@example.com",
        "address": {
          "country": "FR",
          "city": "Paris",
          "region": "Ile-de-France",
          "post_code": "75001",
          "full_address": "1 Main street"
        }
      }
    }
  }
}

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_callback -> optional, boolean - for cascading to work correctly, ignores Constant Payments' asynchronous callback and relies only on an active status request to finalize the payment.
• send_customer_data -> optional, boolean - when enabled, forwards customer data from the request (and the Constants below, for anything missing) to Constant Payments; when disabled, no customer data is sent at all.

Constants (fallback fields)

Constants are static values that Corefy can send to Constant Payments instead of dynamic data from your API request, when those fields are missing in the request and send_customer_data is enabled.

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
• COUNTRY -> customer.address.country
• CITY -> customer.address.city
• STATE -> customer.address.region
• ZIP -> customer.address.post_code
• ADDRESS -> customer.address.full_address
• IP -> customer.metadata.ip
• DESCRIPTION, LANG, REASON -> sent to Constant Payments directly, not mapped from a customer field

Refunds

Constant Payments supports partial refunds, but only one refund per payment (no multiple partial refunds against the same payment). The original transaction ID is required to process a refund.

Connect Provider account in Corefy Dashboard

Uses the same Shop ID / Secret key / Public key credentials as the H2H Merchant account above - no separate connection step if you've already connected the H2H side; otherwise open Constant Payments in the provider directory and press Connect, choosing Provider account.

First request to Corefy API (MIN)

What it does: creates a payout-invoice for a card payout.

Payout - MIN

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "efbf0a2b-5590-42b7-b10b-94d49452147d",
      "service": "payment_card_eur",
      "currency": "EUR",
      "amount": 50,
      "customer": {
        "reference_id": "cus_123"
      },
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

Extended request (MAX)

Why add extra fields (typical reasons): - Provide additional customer details for compliance/reconciliation - Include optional fields required by your specific flow

Constants (fallback fields)

• DESCRIPTION -> sent to Constant Payments directly
• CUSTOMER_NAME -> customer.name
• CUSTOMER_IP -> customer.metadata.ip
• CUSTOMER_EMAIL -> customer.email

Refunds

Constant Payments does not support refunds on Payouts.