Skip to content

Logo

Fenige

ALL ABOUT PAYMENTS

Supports in this guide: Payments

Provider website: fenige.com

What you need to do for start processing transactions (brief summary)

  1. Get your credentials (from Fenige)
  2. Connect in Dashboard
  3. Send an API request

Prerequisites: get from Fenige

Send a connection request at fenige.com or contact your Fenige account manager directly to get your account verified and receive the following credentials.

  • Username -> Corefy field user_login.
  • Password -> Corefy field user_password.
  • Merchant UUID -> Corefy field merchant_uuid.
  • Production API URL (optional) -> Corefy field prod_api_url -> required if you are not using Test Mode.
  • Save instant token (optional) -> Corefy field save_instant_token -> enable to allow saving and charging a card token (see Recurring below).

EUR only.

Payments processing (connect H2H Merchant account, create payment-invoice)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • Username
  • Password
  • Merchant UUID
  • Production API URL (required if Test Mode is disabled)
  • Save instant token (optional)
  • Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected Fenige H2H Merchant account!

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. Fenige may return a 3D Secure challenge depending on the card.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "1f2aa3ca-abd8-4741-980d-4017ed30cb8c",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 5,
      "customer": {
        "reference_id": "85af8385-d00e-4f58-ab1f-3a527fdf2d3b",
        "name": "John Doe",
        "email": "john@example.com"
      }
    }
  }
}

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "1f2aa3ca-abd8-4741-980d-4017ed30cb8c",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 5,
      "customer": {
        "reference_id": "85af8385-d00e-4f58-ab1f-3a527fdf2d3b",
        "name": "John Doe",
        "email": "john@example.com",
        "phone": "+12345678900",
        "address": {
          "full_address": "123 Baker street",
          "country": "US",
          "region": "CA",
          "city": "Los Angeles",
          "post_code": "12345"
        }
      }
    }
  }
}

Important

No Constants are configured for this connector - if a customer field is missing, it's simply not sent.

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_before_clearing -> optional, boolean - finalizes the transaction as soon as it reaches an APPROVED status, without waiting for it to reach CLEARED. Enabled by default.
  • force_auth_for_tokenized_cards -> optional, boolean - enforces mandatory 3D Secure authentication for tokenized cards (such as Apple Pay and Google Pay). Ignored if non-CVV/non-3DS support is enabled on your account.

Refunds

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

Recurring

Fenige supports saving and charging a card token through Corefy, when save_instant_token is enabled on your account.

Additional info

  1. Active reconciliation is available - both the asynchronous callback and an active status request can finalize the payment.
  2. CVV is always required (no CVV-exempt mode) for the initial payment.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify the username, password and Merchant UUID for the selected environment (test_mode)
  • Live payments rejected -> prod_api_url is required once test_mode is disabled
  • Currency or service is not supported -> confirm allowed currencies/features in your Fenige account and in Corefy - only EUR is available
  • Refund fails with multiple attempts -> only one refund per payment is allowed

Question

Still looking for help connecting your Fenige account? Please contact our support team!