Skip to content

PSPGate

PSPGate

Supports in this guide: Payments

Provider website: pspgate.com

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

  1. Choose account type
  2. Get your credentials (from PSPGate)
  3. Connect in Dashboard
  4. Send an API request

Prerequisites: get from PSPGate

Contact your PSPGate account manager to get your merchant account set up and receive the following credentials:

  • Terminal ID -> Corefy field terminal_id
  • Client ID -> Corefy field client_id
  • Client Secret -> Corefy field client_secret
  • Username -> Corefy field username
  • Password -> Corefy field password
  • API Password -> Corefy field api_password - not used for authentication; PSPGate uses it to sign payment callbacks, and Corefy verifies every callback's signature against it

Important

Be sure to check with your account manager if you require to provide a white list of IPs, and if so, specify IP addresses from the Corefy list.

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

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • Terminal ID
  • Client ID
  • Client Secret
  • Username
  • Password
  • API Password
  • Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected PSPGate 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": "1a2b3c4d-5e6f-4a7b-8c91-2d3e4f5a6b7c",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "address": {
          "country": "DE"
        }
      }
    }
  }
}

Important

customer.address.country is required on every request, even a minimal one. Corefy uses it to look up the customer's phone dialing code before building the request to PSPGate; if it's missing, the payment fails internally before ever reaching PSPGate, instead of being sent with an empty value.

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "2b3c4d5e-6f7a-4b8c-8d02-3e4f5a6b7c8d",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "john.smith@example.com",
        "phone": "+491234567890",
        "address": {
          "country": "DE",
          "city": "Berlin",
          "street": "Hauptstrasse 1",
          "post_code": "10115"
        }
      }
    }
  }
}

Important

If both the card's own embossed holder name and customer.name are missing, or end up empty once Corefy strips non-letter characters, a fixed placeholder name John Doe (first name "John", last name "Doe") is sent to PSPGate instead - as the card holder name and as the customer/billing first and last name fields. There's no Dashboard override for this.

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

PSPGate does not support refunds through Corefy - the connector has no refund capability implemented.

Recurring

Not supported - this connector cannot save or charge a card token through Corefy.

Additional info

  1. 3D Secure is not supported - if the card requires 3D Secure authentication, the sale request fails immediately instead of being sent to PSPGate.
  2. A valid CVV is required on every sale - a request without one is rejected by Corefy before reaching PSPGate.
  3. Active reconciliation is available in addition to the asynchronous callback - Corefy can proactively query PSPGate for the current status of a payment.
  4. Payment callbacks from PSPGate are signature-verified: PSPGate signs each callback with a hash of the order ID and your API Password, and Corefy checks it before accepting the callback.
  5. Supported currencies: EUR, USD, AZN.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify Terminal ID, Client ID, Client Secret, Username, and Password match the selected environment (Test Mode)
  • Payment fails for a specific card with no clear reason -> the card may require 3D Secure authentication, which this connector does not support
  • Callback rejected as invalid signature -> confirm the API Password on the connected account matches the one configured on your PSPGate terminal
  • Reconciliation request fails -> reconciliation requires the original PSPGate transaction ID from a prior sale response; it cannot be used before a sale has been attempted

Question

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