Creditum (new)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

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

EUR only.

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": "5e6f7a81-2b3c-4d5e-8f93-4a5b6c7d8e9f",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6f7a8b92-3c4d-4e5f-8a04-5b6c7d8e9f0a",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "date_of_birth": "1990-05-20",
        "address": {
          "country": "FR",
          "region": "IDF",
          "city": "Paris",
          "full_address": "1 Main street",
          "post_code": "75000"
        }
      }
    }
  }
}

customer is entirely optional. For first/last name, the priority is the name embossed on the card, then 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

Options

• ignore_callback -> optional, boolean - for cascading to work correctly, excludes finalizing the payment from the asynchronous callback; Corefy then relies only on an active status request (reconciliation) to finalize it.
• finalize_by_protocol -> optional, boolean - the provider doesn't always guarantee that a declined status is final (it can later change to a success on their side); enable this if you'd rather have Corefy treat a decline as final immediately instead of waiting.
• save_provider_instant_token -> optional, boolean - enable to allow recurring charges on this connection.
• send_additional_data -> optional, boolean - sends extra metadata with the sale.

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
• 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

Recurring (save and charge a token)

If Save Provider Instant Token is enabled on your connection, a sale is registered as card-on-file; a later charge can reuse that stored card without sending full card data again.

Refunds

Creditum (new) supports partial and multiple refunds against the same payment.

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

Open Creditum (new) in the provider directory and press Connect at Creditum (new) Provider Overview page in the New connection section. Choose Provider account.

Step 2 - Fill in fields and select settings

• API Key
• Signing Key
• API 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 Creditum-hosted page to complete the payment. Available methods - Przelewy24 (PLN), Paysafecard, Skrill, Neteller, EPS, iDEAL, MB WAY, Multibanco, MyBank, RapidTransfer, ePay (BGN and EUR), Klarna bank transfer, Bancontact (all EUR unless noted) - depend on what's enabled for your account.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "7a8b9c03-4d5e-4f6a-8b15-6c7d8e9f0a1b",
      "service": "przelewy24_pln_hpp",
      "currency": "PLN",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8b9c0d14-5e6f-4a7b-8c26-7d8e9f0a1b2c",
      "service": "przelewy24_pln_hpp",
      "currency": "PLN",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "date_of_birth": "1990-05-20",
        "address": {
          "country": "PL",
          "region": "Mazowieckie",
          "city": "Warsaw",
          "full_address": "1 Main street",
          "post_code": "00-001"
        }
      }
    }
  }
}

customer is entirely optional - everything is only used to prefill the hosted form, 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

Options

• finalize_by_protocol -> optional, boolean - same meaning as on the H2H Merchant account above: treats a declined status as final immediately instead of waiting for it to possibly change.
• time_to_finalize -> optional, number - if an active status check finds the payment still pending after this many minutes since creation, reports it as failed/expired instead of leaving it pending indefinitely.

Constants (fallback fields)

Same priority rule and field list as the H2H Merchant account above, plus:

• locale -> customer.metadata.locale (defaults to en if neither is set)
• routing_group, payment_method -> internal routing values; Corefy automatically fills these with the selected payment method's own code, so you don't need to set them unless your account manager asks you to use a different value for a specific route.

Refunds

This connector does not support refunds on the Provider account - use the H2H Merchant account if you need refunds.