Sola

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Project ID
• Secret key
• Currency / Features -> choose values available for your account (EUR)

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. The flow is always 3D Secure (non-3DS and a configurable 3DS control version are not supported), and CVV is always required (no CVV-exempt mode).

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "1f2aa3ca-abd8-4741-980d-4017ed30cb8c",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 5,
      "customer": {
        "reference_id": "85af8385-d00e-4f58-ab1f-3a527fdf2d3b"
      }
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "c7513313-648f-422d-b17d-8884606f22c3",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 5,
      "customer": {
        "reference_id": "85af8385-d00e-4f58-ab1f-3a527fdf2d3b",
        "name": "John Doe",
        "email": "johndoe@mail.com",
        "phone": "+2134234234523",
        "date_of_birth": "1990-05-20",
        "address": {
          "country": "US",
          "region": "New York",
          "city": "Los Angeles",
          "street": "5th Avenue 1",
          "post_code": "10001"
        }
      }
    }
  }
}

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

• generate_data_for_customer -> optional, boolean - when enabled, any of country/city/phone/first_name/last_name/email/address/zip/state/day_of_birth still missing after the request and Constants are applied are filled with a fixed placeholder value (not a unique/random value per request - every merchant with this option enabled sends the same filler data for a given field, e.g. email: test@test.test, phone: +380989009090, city: La Chorrera). Data actually sent by the customer or resolved from a Constant is never overwritten.

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 if generate_data_for_customer is enabled -> Corefy uses the fixed placeholder described above 4. Else -> the field is sent to Sola as null

Currently available constants (constant -> Corefy API field)

• CUSTOMER_COUNTRY -> customer.address.country
• CUSTOMER_CITY -> customer.address.city
• CUSTOMER_PHONE -> customer.phone
• CUSTOMER_FIRST_NAME -> customer.name (first name part)
• CUSTOMER_LAST_NAME -> customer.name (last name part)
• CUSTOMER_EMAIL -> customer.email
• CUSTOMER_ADDRESS -> customer.address.full_address / .street
• CUSTOMER_ZIP -> customer.address.post_code
• CUSTOMER_STATE -> customer.address.region
• CUSTOMER_DAY_OF_BIRTH -> customer.date_of_birth (format DD-MM-YYYY)

Refunds

Sola does not support refunds.