PXP

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Merchant ID
• Shop ID
• Username
• Password
• Test Mode -> (enable if you are using sandbox credentials)
• Callback IP Whitelist (optional) -> see the important note under Options below
• Finalize by Auth (optional)
• Finalize After (minutes) (optional)

Choose Currency / Features; check with your Corefy account manager which currencies and methods are enabled for your account - this connector isn't restricted to a fixed currency list.

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. PXP performs full EMV 3D Secure 2 authentication, including a device-fingerprinting step, and may require a challenge redirect before the sale completes. CVV is always required - non-CVV sales aren't supported.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8e3dbbb0-17af-4c9a-bedb-93bdac6900a2",
      "service": "payment_card_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": "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-01-01",
        "address": {
          "country": "FR",
          "city": "Paris",
          "full_address": "1 Main street",
          "post_code": "75000"
        }
      }
    }
  }
}

customer is entirely optional - anything you don't send falls back to the Constants below, or is simply left blank on PXP's side.

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.
• allow_finalyze_by_auth -> optional, boolean (labeled Finalize by Auth on the connect form) - by default, Corefy waits for PXP's capture confirmation before reporting a sale as a final success; enable this to treat a successful authorization alone as final, without waiting for capture.
• finalize_after_minutes -> optional, number (labeled Finalize After (minutes)) - if a reconciliation check still shows the payment pending this many minutes after it was created, Corefy gives up waiting and reports it as a timed-out failure instead of checking indefinitely. Useful if customers sometimes abandon the 3D Secure challenge page.
• callback_ip_whitelist -> optional, string (labeled Callback IP Whitelist) - the IP address(es) PXP sends callbacks from.

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
• COUNTRY_CODE -> customer.address.country
• FULL_ADDRESS -> customer.address.full_address
• POST_CODE -> customer.address.post_code
• LANGUAGE_CODE -> language of PXP-side communication; defaults to English if not set
• GENDER -> Male or Female; sent to PXP if set, since Corefy's own customer object has no standard gender field

Refunds

PXP supports partial and multiple refunds against the same payment.