PSPARK

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• API Key
• Public Key
• Private Key
• API URL (optional)
• API S2S URL (optional)
• 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 a PSPARK-hosted page to complete the payment via BLIK, bank transfer, or African mobile money, depending on what's enabled for your account.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "7a1c3e5f-9b0d-4a2c-8e4f-6a8c0e2f4a6c",
      "service": "blik_pln_hpp",
      "currency": "PLN",
      "amount": 20
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8b2d4f60-0c1e-4b3d-8f5a-7b9d1f3a5c7e",
      "service": "blik_pln_hpp",
      "currency": "PLN",
      "amount": 20,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "date_of_birth": "1990-01-01",
        "individual_tax_id": "12345678900",
        "address": {
          "country": "PL",
          "region": "Mazovia",
          "city": "Warsaw",
          "full_address": "1 Main street",
          "post_code": "00-001"
        },
        "metadata": {
          "ip": "203.0.113.5",
          "client_agent": "Mozilla/5.0",
          "payment_purpose": "goods",
          "national_id": "32"
        }
      }
    }
  }
}

customer is entirely optional - anything you don't send falls back to the Constants below.

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

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)

• description -> a static description sent with every payment (not tied to a request field)
• first_name -> customer.first_name
• last_name -> customer.last_name
• email -> customer.email
• phone -> customer.phone
• customer_reference_id -> customer.reference_id
• full_address -> customer.address.full_address
• country_code / country -> customer.address.country
• city -> customer.address.city
• post_code -> customer.address.post_code
• region -> customer.address.region
• street -> customer.address.street
• ip -> customer.metadata.ip
• user_agent -> customer.metadata.client_agent
• individual_tax_id -> customer.individual_tax_id
• birth_date -> customer.date_of_birth
• payment_purpose -> customer.metadata.payment_purpose
• national_id -> customer.metadata.national_id

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 BLIK, card, bank transfer, M10, or African mobile money (Airtel Money, Safaricom/M-Pesa, T-Kash), depending on what's enabled for your account. Required fields vary by method - the Dashboard shows the exact field list once a method is selected.

Payout - MIN

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "9c3e5f71-1d2e-4c4f-8a6b-8c0e2f4a6c8e",
      "service": "blik_pln",
      "currency": "PLN",
      "amount": 20,
      "fields": {}
    }
  }
}

Payout - MAX

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "0d4f6082-2e3f-4d5a-8b7c-9d1f3a5c7e9f",
      "service": "blik_pln",
      "currency": "PLN",
      "amount": 20,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "date_of_birth": "1990-01-01",
        "individual_tax_id": "12345678900",
        "address": {
          "country": "PL",
          "region": "Mazovia",
          "city": "Warsaw",
          "full_address": "1 Main street",
          "post_code": "00-001"
        }
      },
      "fields": {}
    }
  }
}

customer is entirely optional - everything is only forwarded to PSPARK as recipient details, with the same fallback Constants as Payments. For Airtel Money, Safaricom, and T-Kash payouts specifically, a fields.phone value (if sent) takes priority over customer.phone.

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

• payout_failed -> optional, boolean - if PSPARK's initial response reports one of its known failure codes, reports the payout as a definitive failure right away instead of leaving it as a generic error.