JM IT Solutions

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Merchant private key
• Currency / Features -> choose values available for your account (EUR, USD)

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. Card, Apple Pay, and Google Pay are all supported on this same connection, with Apple Pay/Google Pay decryption on the Corefy side.

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": "199be985-c243-478a-86a8-4b8c902e5bb6",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Doe",
        "email": "test@test.com",
        "phone": "+380680786663",
        "date_of_birth": "1990-01-01",
        "address": {
          "full_address": "Main street 1",
          "country": "GB",
          "city": "London",
          "region": "London",
          "post_code": "W1J 5AX"
        }
      }
    }
  }
}

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 JM IT Solutions' asynchronous callback and relies only on an active status request to finalize the payment.

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
• FIRST_NAME, LAST_NAME, PHONE -> exposed in the Dashboard, but have no effect on this connector's requests

Refunds

JM IT Solutions supports partial refunds, but only one refund per payment (no multiple partial refunds against the same payment).