Inpay

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Account Number
• Account UUID
• Account Token
• Private Key
• Private SSL Certificate
• Public SSL Certificate
• SSL Certificate Chain
• Test Mode -> (enable if you are using sandbox credentials)

First request to Corefy API (MIN)

What it does: creates a payment-invoice and redirects the customer to their own bank via Inpay's Open Banking flow to authorize a payment. EUR only.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "3d4e5f60-7a8b-4c9d-8e01-2f3a4b5c6d7e",
      "service": "openbanking_eur_hpp",
      "currency": "EUR",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "4e5f6a71-8b9c-4d0e-8f12-3a4b5c6d7e8f",
      "service": "openbanking_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "date_of_birth": "1990-05-20",
        "address": {
          "country": "DE"
        }
      }
    }
  }
}

customer is entirely optional - everything is only used to prefill Inpay's own Open Banking flow, it never blocks the sale.

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

No Options are configured for this connector.

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 (first part)
• last_name -> customer.name (second part)
• email -> customer.email
• country -> customer.address.country
• date_of_birth -> customer.date_of_birth

Refunds

This connector does not support refunds.

Connect Provider account in Corefy Dashboard

Uses the same Provider account connection as Payments above - one connection covers both directions, nothing extra to fill in for payouts specifically.

First request to Corefy API (MIN)

What it does: creates a payout-invoice and sends funds via SEPA transfer or local bank transfer, depending on the currency. EUR and several Gulf currencies are supported.

Payout - MIN

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "5f6a7b82-9c0d-4e1f-8a23-4b5c6d7e8f9a",
      "service": "sepa_transfer_eur",
      "currency": "EUR",
      "amount": 10,
      "fields": {
        "account_number": "DE89370400440532013000",
        "beneficiary_first_name": "John",
        "beneficiary_last_name": "Doe",
        "beneficiary_country": "DE"
      }
    }
  }
}

This connector also supports BHD, AED, SAR, KWD, QAR, OMR.

Payout - MAX

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "6a7b8c93-0d1e-4f2a-8b34-5c6d7e8f9a0b",
      "service": "sepa_transfer_eur",
      "currency": "EUR",
      "amount": 10,
      "fields": {
        "account_number": "DE89370400440532013000",
        "beneficiary_first_name": "John",
        "beneficiary_last_name": "Doe",
        "beneficiary_country": "DE",
        "beneficiary_city": "Berlin",
        "beneficiary_address": "1 Main street",
        "beneficiary_postcode": "10115",
        "beneficiary_state": "Berlin",
        "beneficiary_date_of_birth": "1990-05-20",
        "bank_bic": "COBADEFFXXX"
      }
    }
  }
}

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

No Options are configured for this flow.

Constants (fallback fields)

For payouts, Constants cover two roles: the beneficiary (recipient) fields below, used as a fallback for the matching fields.beneficiary_* above, and the debtor_* fields, which are YOUR OWN sender details - normally taken automatically from your Corefy merchant profile (company name/address/city/country/region), with these constants only as a fallback for when that's not set.

Available constants (constant -> meaning)

• name -> beneficiary full name (fallback for fields.beneficiary_first_name+beneficiary_last_name/beneficiary_full_name)
• bank_bic -> beneficiary bank BIC
• city -> beneficiary city
• country -> beneficiary country
• state -> beneficiary state
• full_address -> beneficiary address
• post_code -> beneficiary post code
• date_of_birth -> beneficiary date of birth
• debtor_name -> your own (sender) name -> falls back from your merchant profile's company name
• debtor_city -> your own city
• debtor_country -> your own country
• debtor_state -> your own region
• debtor_full_address -> your own address
• debtor_post_code -> your own post code
• debtor_date_of_birth -> your own date of birth (no merchant profile source - constant only)