ConnPay New

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Token -> token
• ID requestor -> requestor_id
• API url -> api_url
• Test mode -> (enable if you are using sandbox credentials - requests are then sent to ConnPay New's test environment and the API url value is not used)
• Choose Currency and Features. You can set these parameters according to available currencies and features for your ConnPay New account, but it is necessary to check details of the connection with your Corefy account manager.

First request to Corefy API (MIN)

What it does: creates a payment-invoice.

Corefy does not enforce any payer fields for this connector - a request without a customer block is accepted and forwarded. ConnPay New itself expects full payer details (name, email, phone, date of birth, billing address) for a real transaction, so send them per request as shown in MAX, or configure them once as Constants (see below).

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "276bead5-f81d-4b91-9512-63b725ba9b58",
      "service": "payment_card_eur_hpp",
      "commerce_account": "coma_JV9plJV3qn44UZ2t",
      "currency": "EUR",
      "amount": 10,
      "flow": "charge",
      "test_mode": false
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "276bead5-f81d-4b91-9512-63b725ba9b58",
      "service": "payment_card_eur_hpp",
      "commerce_account": "coma_JV9plJV3qn44UZ2t",
      "currency": "EUR",
      "amount": 10,
      "flow": "charge",
      "gateway_options": {
        "cardgate": {
          "tokenize": false
        }
      },
      "customer": {
        "reference_id": "817a00b0-0a83-4afa-abba-08254faebc93",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+37060000000",
        "date_of_birth": "1990-01-20",
        "address": {
          "full_address": "Gedimino pr. 10, Apt. 8",
          "country": "LT",
          "region": "LT-VL",
          "city": "Vilnius",
          "post_code": "01103"
        },
        "metadata": {
          "website_url": "https://example.com"
        }
      },
      "test_mode": false,
      "options": {
        "allow_partially": true,
        "bypass_hpp": false,
        "send_operation_context_on_return": false
      },
      "service_fields": []
    }
  }
}

customer.metadata.website_url is sent to ConnPay New as the payment's source site. If it is not provided, Corefy falls back to the merchant profile's own website URL.

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 (4)

• ignore_callback - skip processing of ConnPay New callbacks for this account
• extended_threeds_data_waiting_time - wait longer for the redirect/3DS data before giving up
• pending_refunds_on_invalid_response - report a refund as pending instead of error when the provider's response cannot be parsed
• prioritize_cardholder - take the payer's first/last name from the cardholder data instead of the customer object

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)

• FIRST_NAME -> customer.name
• LAST_NAME -> customer.name
• EMAIL -> customer.email
• PHONE -> customer.phone
• DATE_OF_BIRTH -> customer.date_of_birth
• COUNTRY -> customer.address.country
• REGION -> customer.address.region
• POST_CODE -> customer.address.post_code
• CITY -> customer.address.city
• ADDRESS_LINE_1 -> customer.address.full_address
• ADDRESS_LINE_2 -> customer.address.full_address

FIRST_NAME and LAST_NAME both back customer.name - Corefy splits that single value into first and last name, so each half has its own constant.