Payneteasy

Leading Payment Platform Provider

Supports in this guide: Payments, Payouts

Provider website: payneteasy.com

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

Choose account type
Get your credentials (from Payneteasy)
Connect in Dashboard
Send an API request

Choose account type

Payneteasy can be connected in different ways (depending on your needs):

If you do H2H card payments (card data sent directly) -> choose H2H Merchant account
If you do local bank-transfer/open-banking payments -> choose Merchant account
If you do payouts -> choose Provider account

If you're not sure which one to use, confirm with your Corefy account manager.

Prerequisites: get from Payneteasy

Submit a connection request at payneteasy.com/contacts or contact your Payneteasy account manager directly to get your account verified and receive the following credentials.

For H2H Merchant account:

Login -> Corefy field login.
Control Key -> Corefy field control_key -> used to sign every request.
Endpoint ID -> Corefy field endpoint_id.
API URL (optional) -> Corefy field api_url.

For Merchant account:

Login -> Corefy field login.
Control Key -> Corefy field control_key.
Endpoint ID -> Corefy field endpoint_id.

For Provider account:

Login -> Corefy field login.
Control Key -> Corefy field control_key.
Private Key (optional, file upload) -> Corefy field private_key.
Endpoint ID (optional) -> Corefy field endpoint_id.

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

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

Login
Control Key
Endpoint ID
API URL (optional)
Use API URL Path (optional)
Multiple Currency Integration
Test Mode -> (enable if you are using sandbox credentials)

Choose Currency and Features. EUR, USD, CAD, and AUD are confirmed; check with your Corefy account manager which are enabled for your account.

Success

You have connected Payneteasy 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.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8e3dbbb0-17af-4c9a-bedb-93bdac6900a2",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "date_of_birth": "1990-01-01",
        "address": {
          "country": "US",
          "city": "New York",
          "full_address": "1 Main street",
          "post_code": "10001"
        }
      }
    }
  }
}

Important

customer is technically optional, but you should still always send it: anything you omit falls back to the Constants below, and anything missing from both the request and Constants is replaced with a hardcoded German placeholder address/phone/email rather than failing the request. A real transaction needs real customer/billing data to actually be accepted - the placeholder exists only so the request has some value in every field, not as a usable fallback for production traffic.

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

Options are configured on the Corefy side and affect how Corefy builds provider requests or processes responses.

Currently available options (3)

ignore_callback - tells Corefy to disregard Payneteasy's own callback notifications entirely.
use_default_browser_info - falls back to the Constants below for browser/3DS metadata when the real browser data isn't available.
custom_finalization_logic - treats an approved sale as successful even if Payneteasy's response also carries an error field.

ignore_callback

What it does: when enabled, Corefy ignores callback notifications sent by Payneteasy for this connection, relying on status checks/reconciliation instead.

When to use: enable only if instructed by Payneteasy or your Corefy account manager.

Default: false

Allowed values: true / false

use_default_browser_info

What it does: when enabled, any browser/3DS fingerprint field not captured from the customer's actual browser (screen size, color depth, language, timezone, user agent, etc.) falls back to the matching Constant below instead of being left blank.

When to use: enable it if your checkout doesn't always capture full browser data and you'd rather send a fallback than an incomplete fingerprint.

Default: false

Allowed values: true / false

custom_finalization_logic

What it does: Payneteasy occasionally returns an APPROVED status alongside an error field on the same response. By default Corefy treats any response carrying an error field as failed; enabling this option makes an APPROVED status win regardless.

When to use: enable only if instructed by Payneteasy or your Corefy account manager - typically needed if you're seeing approved transactions reported as failed.

Default: false

Allowed values: true / false

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)

ADDRESS -> customer.address.full_address
CITY -> customer.address.city
ZIP -> customer.address.post_code
COUNTRY -> customer.address.country
PHONE -> customer.phone
EMAIL -> customer.email
DATE_OF_BIRTH -> customer.date_of_birth
Browser/3DS metadata constants (only used if use_default_browser_info is enabled): browser language, screen width/height, color depth, timezone offset, user agent, accept header, Java-enabled flag, and IP.

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

Connect Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

Login
Control Key
Endpoint ID
Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected Payneteasy Merchant account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice and returns a redirect link to the bank-transfer or open-banking payment page.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8e3dbbb0-17af-4c9a-bedb-93bdac6900a2",
      "service": "bank_transfer_aggregated_eur_hpp",
      "currency": "EUR",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "bank_transfer_aggregated_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "Johann Müller",
        "email": "johann.mueller@example.de",
        "phone": "+498912345678",
        "address": {
          "full_address": "Goethestraße 17",
          "city": "München",
          "country": "DE",
          "post_code": "80336"
        }
      }
    }
  }
}

customer is optional - anything you omit falls back to the Constants below. This connector also supports USD, CLP, MXN, and ARS (use bank_transfer_aggregated_<ccy>_hpp as the service code), plus Open Banking in EUR (use openbanking_eur_hpp).

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

Options are configured on the Corefy side and affect how Corefy builds provider requests or processes responses. Available only for bank_transfer_aggregated_usd_hpp/bank_transfer_aggregated_eur_hpp.

Currently available options (3)

status_requests_number - how many times Corefy polls Payneteasy for a status update (1-10).
status_requests_delay - how many seconds Corefy waits between each status poll (1-5).
site_url_metadata_key - which metadata key holds the website URL to send with the payment.

status_requests_number / status_requests_delay

What they do: together they control how persistently Corefy polls Payneteasy for a final status on a pending payment - up to status_requests_number attempts, status_requests_delay seconds apart.

When to use: tune these if your account manager advises a different polling cadence than the platform default.

Default: not set (platform default applies)

Allowed values: status_requests_number: 1-10; status_requests_delay: 1-5 (seconds)

site_url_metadata_key

What it does: tells Corefy which key in your request's metadata object holds your website URL, so it can forward it to Payneteasy.

When to use: set it if Payneteasy requires your site URL and you pass it under a custom metadata key rather than relying on your merchant profile's website.

Default: not set

Allowed values: any metadata key name

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. Available for bank_transfer_aggregated_usd_hpp/eur_hpp/clp_hpp/mxn_hpp/ars_hpp and openbanking_eur_hpp.

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)

ADDRESS -> customer.address.full_address
CITY -> customer.address.city
ZIP -> customer.address.post_code
COUNTRY -> customer.address.country
PHONE -> customer.phone
EMAIL -> customer.email
FIRST_NAME -> customer.name (first part)
LAST_NAME -> customer.name (second part)
IP -> customer.metadata.ip
URL -> your website URL (see site_url_metadata_key above)

Payouts processing (connect Provider account, create payout-invoice)

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

Login
Control Key
Private Key (optional, file upload)
Endpoint ID (optional)
Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected Payneteasy Provider account!

First request to Corefy API (MIN)

What it does: creates a payout-invoice and sends funds to a card, a bank account, or via Interac e-Transfer.

Payout - MIN (card)

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "0dde9e79-2c64-4703-adaf-93d710633401",
      "service": "payment_card_usd",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith"
      },
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

fields.card_number is required; the cardholder's name is derived from customer.name. This connector also supports card payouts in EUR/AUD/NZD (use payment_card_<ccy> as the service code), bank transfer in CLP/MXN (use bank_transfer_<ccy>), and Interac e-Transfer in EUR/CAD (use interac_<ccy>).

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

Options are configured on the Corefy side and affect how Corefy builds provider requests or processes responses.

Currently available options (1)

payout_api_version - which Payneteasy payout API generation Corefy uses for this connection.

payout_api_version

What it does: selects which version of Payneteasy's payout API Corefy calls for this connection.

When to use: set it to match what Payneteasy's account manager confirms your account is provisioned for.

Default: v1

Allowed values: v1 / v2

No Constants are configured for this flow.

Additional info

Callback routing. For H2H Merchant account and Merchant account, callback routing is handled automatically - Corefy generates the callback URL per transaction. For Provider account (Payouts), callback routing is also automatic.

FAQ / Troubleshooting

Invalid credentials / auth error -> verify credentials for the selected environment and account type
H2H payment accepted with wrong customer/billing data -> always send real customer data; omitted fields are silently replaced by a placeholder German address rather than failing
Approved transaction reported as failed -> try enabling custom_finalization_logic on the H2H Merchant account
Currency or service is not supported -> confirm allowed currencies/features in your Payneteasy account and in Corefy
Not sure which account type to use? -> ask your Corefy account manager

Question

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