Paymaster

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields

• Private key

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. Only RUB is supported on this flow.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6be05631-8710-4b14-a369-1928a2b70eda",
      "service": "payment_card_rub_hpp",
      "currency": "RUB",
      "amount": 1200
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "199be985-c243-478a-86a8-4b8c902e5bb6",
      "service": "payment_card_rub_hpp",
      "currency": "RUB",
      "amount": 1200,
      "customer": {
        "reference_id": "cus_123",
        "email": "test@test.com",
        "phone": "+79991234567",
        "date_of_birth": "1990-05-20",
        "address": {
          "full_address": "1 Tverskaya street",
          "country": "RU",
          "city": "Moscow",
          "region": "Moscow",
          "post_code": "125009"
        }
      }
    }
  }
}

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 -> Corefy uses its own hardcoded fallback (EMAIL only) or omits the field

Currently available constants (constant -> Corefy API field)

• EMAIL -> customer.email (falls back to hardcoded test@gmail.com if neither is set)

Options

• ignore_callback -> boolean, optional - stops Corefy from finalizing the transaction via the asynchronous callback; the transaction is finalized only by an active status request (Reconciliation) instead. Useful for cascading setups, where an early callback would finalize a transaction prematurely.

Refunds

Paymaster supports partial refunds, but only one refund per payment (multiple sequential refunds are not allowed). The original transaction ID is required to process a refund.

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• API key
• Signing key
• Test Mode -> (enable if you are using sandbox credentials)

First request to Corefy API (MIN)

What it does: creates a payment-invoice for a BLIK payment and redirects the customer to complete it. Only EUR and PLN are supported on this flow.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "efbf0a2b-5590-42b7-b10b-94d49452147d",
      "service": "blik_eur_hpp",
      "currency": "EUR",
      "amount": 10.04
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "1f2aa3ca-abd8-4741-980d-4017ed30cb8c",
      "service": "blik_pln_hpp",
      "currency": "PLN",
      "amount": 10.04,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Doe",
        "email": "test@test.com",
        "phone": "+48123456789",
        "date_of_birth": "1990-05-20",
        "address": {
          "full_address": "1 Marszalkowska street",
          "country": "PL",
          "city": "Warsaw",
          "region": "Mazowieckie",
          "post_code": "00-001"
        }
      }
    }
  }
}

None of the customer fields are mandatory - every one of them is sent to Paymaster only when present, and can be replaced by a Constant (see 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 -> the field is omitted from the request

Currently available constants (constant -> Corefy API field)

• FIRST_NAME -> customer.name (first part of the name)
• LAST_NAME -> customer.name (last part of the name)
• EMAIL -> customer.email
• PHONE -> customer.phone
• DATE_OF_BIRTH -> customer.date_of_birth
• CITIZENSHIP_COUNTRY_CODE -> customer.address.country
• FULL_ADDRESS -> customer.address.full_address
• CITY -> customer.address.city
• COUNTRY_CODE -> customer.address.country
• POSTAL_CODE -> customer.address.post_code
• STATE -> customer.address.region
• LOCALE -> customer's checkout locale (defaults to en if unset)

Options

• finalize_by_protocol -> boolean, optional, default false - when Paymaster returns a declined status, Corefy treats it as final immediately instead of keeping the transaction pending. Paymaster does not guarantee a decline is final (it can later flip to success on their side) - enable this only if you accept a decline as final.

Refunds

Paymaster does not support refunds on the Provider account (BLIK) flow.