MF Stream

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Shop ID
• Public key
• Secret key
• 3DS mode -> Simple or Advanced
• Test Mode -> (enable if you are using sandbox credentials)
• Currency / Features -> choose values available for your account (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.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "86e68af6-6b95-4cc0-be16-e4df8044604c",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "08f5e97c-1170-4bda-9625-3bde3c6dcd20",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "bc75bc54-5023-4f98-8c0d-ec5ed7e8f380",
        "name": "John Doe",
        "email": "test@test.com",
        "phone": "+380680786663",
        "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 MF Stream's asynchronous callback and relies only on an active status request to finalize the payment.
• send_customer_data -> optional, boolean - when enabled, forwards customer.name/.phone/.address (country/city/region/post_code) to MF Stream as billing address fields; falls back to the matching Constants (or cardholder name from the card itself) when a field is missing.
• duplicate_check -> optional, boolean, default false - when enabled, rejects a repeat charge request with the same amount and card/token sent within 30 seconds of the original request.

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 -> Corefy falls back to a fixed default value (see below) for EMAIL/DESCRIPTION/LANG; for the billing-address constants, the field is simply omitted unless send_customer_data is enabled

Currently available constants (constant -> Corefy API field)

• EMAIL -> customer.email
• DESCRIPTION -> transaction description (not tied to a request field - set a default description for MF Stream's own records)
• LANG -> checkout page language code
• REASON -> refund reason text sent to MF Stream
• COUNTRY, CITY, STATE, ZIP, ADDRESS -> customer.address.country/.city/.region/.post_code/.full_address - only applied when send_customer_data is enabled
• IP -> exposed in the Dashboard, but has no effect on this connector's requests

Refunds

MF Stream supports partial refunds, but only one refund per payment (no multiple partial refunds against the same payment).