Skip to content

Logo

Benker

Supports in this guide: Payments

Provider website: benker.io

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

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

Prerequisites: get from Benker

Send a connection request at benker.io or contact your Benker manager directly to get your account verified and receive the following credentials.

  • Project ID -> Corefy field project_id.
  • Secret Key -> Corefy field secret_key.

Available currencies/services are auto-discovered live from your Benker account - confirm with your account manager which open banking routes apply to you.

Payments processing (connect Provider account, create payment-invoice)

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • Project ID
  • Secret Key
  • Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected Benker Provider account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice and redirects the customer to Benker's hosted payment page.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "1f2aa3ca-abd8-4741-980d-4017ed30cb8c",
      "service": "openbanking_eur_hpp",
      "currency": "EUR",
      "amount": 5
    }
  }
}

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "2a3bb4db-bce9-4852-891e-5128fe41dc9d",
      "service": "openbanking_eur_hpp",
      "currency": "EUR",
      "amount": 5,
      "customer": {
        "reference_id": "1dc26f5a-a361-499b-9533-39625b59ab73",
        "name": "Test Test"
      }
    }
  }
}

Important

  • customer.reference_id and customer.name (split into first/last name) are forwarded to Benker, when provided.
  • No Options or Constants are configured for this connector.

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

Refunds

Benker does not support refunds.

Additional info

  1. Active reconciliation is available - an active status request can be used in addition to the asynchronous callback.
  2. No recurring - this connector does not support saving/charging a token through Corefy.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify Project ID and Secret Key for the selected environment (test_mode)
  • Currency or service is not supported -> confirm allowed currencies/features in your Benker account and in Corefy
  • Refund fails -> Benker does not support refunds through Corefy

Question

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