Networx

Supports in this guide: Payments

Provider website: networx.pro

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

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

Choose account type

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

If you do card payments -> choose H2H Merchant account

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

Prerequisites: get from Networx

Get the following values for your Networx project/account:

Shop ID -> Corefy field shop_id -> example: shop_9f2c1a3b -> where to find: Networx backoffice / issued by Networx manager
Public Key -> Corefy field public_key -> example: pk_live_7d3f8b2a9c1e4560 -> where to find: Networx backoffice / issued by Networx manager
Secret Key -> Corefy field secret_key -> example: sk_live_4a6e2d9f1b3c8720 -> where to find: Networx backoffice / issued by Networx manager
API URL -> Corefy field api_url -> example: https://gateway.networxpay.com -> where to find: Networx backoffice / issued by Networx manager, only needed to override the default provider URL

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

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

Shop ID
Public Key
Secret Key
Three DS Mode -> (Simple or Advanced — defaults to Advanced if not set)
Provider URL -> (preset to Networx's gateway, not user-selectable)
API URL -> (optional — override the default provider URL)
Test Mode -> (enable if you are using sandbox credentials)

Choose Currency and Features. You can set these parameters according to available currencies and features for your Networx account, but it is necessary to check details of the connection with your Corefy account manager.

Success

You have connected Networx H2H Merchant account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 100,
      "customer": {
        "reference_id": "55041b5b-adfd-4073-a92b-fd8b495a4cc1",
        "email": "johnsmith@gmail.com"
      },
      "reference_id": "86e68af6-6b95-4cc0-be16-e4df8044604c"
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 100,
      "customer": {
        "reference_id": "bc75bc54-5023-4f98-8c0d-ec5ed7e8f380",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "date_of_birth": "1990-05-14",
        "address": {
          "country": "US",
          "region": "CA",
          "city": "Los Angeles",
          "post_code": "90001",
          "full_address": "1st Street 1"
        },
        "metadata": {
          "website_url": "https://example.com"
        }
      },
      "reference_id": "08f5e97c-1170-4bda-9625-3bde3c6dcd20"
    }
  }
}

The billing address fields above only reach Networx when the send_customer_data option (see Options) is enabled — otherwise only customer.email is used. customer.metadata.website_url is different: it's checked on every request regardless of that option, and when present it replaces the payment description entirely (see Additional info).

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 (7)

ignore_callback - suppresses processing of callbacks received from Networx
send_customer_data - sends the customer's billing details (name, phone, address) to Networx
transliterate_card_holder - transliterates the cardholder name before sending it
transliterate_customer_data - transliterates the customer billing details before sending them
transliterate_request_data - transliterates the full request payload before sending it
generate_random_customer_data - generates random billing details instead of using the real customer data
skip_state_validation - skips validating the billing address state/region against the country

ignore_callback

What it does: when enabled, Corefy ignores callbacks received from Networx instead of processing them.

When to use: if you rely only on reconciliation/status checks and don't want callback-driven updates for this connection.

Default: "false"