paymentsPRO

Supports in this guide: Payments

Provider website: paymentspro.io

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

Get your credentials (from paymentsPRO)
Connect in Dashboard
Send an API request

Prerequisites: get from paymentsPRO

Contact your paymentsPRO account manager to get your account verified and receive the following credentials.

Header token -> Corefy field header_token.
Auth key -> Corefy field auth_key - updatable after the account is connected.

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

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

Header token
Auth key
Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected paymentsPRO H2H Merchant account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice for a direct card (H2H) sale; 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": "87b1530a-6c53-4aac-9422-a90fb41a1631",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 100
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "199be985-c243-478a-86a8-4b8c902e5bb6",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 100,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Doe",
        "email": "johndoe@example.com",
        "phone": "+447912345678",
        "address": {
          "full_address": "1 Main street",
          "country": "GB",
          "city": "London",
          "region": "London",
          "post_code": "SW1A 1AA"
        }
      }
    }
  }
}

Important

Only Visa and Mastercard card networks are processed.
Depending on the issuing bank's response, paymentsPRO may approve the sale directly or require a 3-D Secure redirect - Corefy drives the redirect/return flow for you transparently, you don't need to branch your integration for it.
The whole customer object, and every field inside it, is optional - if customer.name/.email/.phone/.address is missing, paymentsPRO simply does not receive that field unless a matching Constant is set (see Constants below). If customer.name is missing, the name is instead taken from the cardholder name on the card.

Extended request (MAX)

Why add extra fields (typical reasons): - Provide billing address/contact details paymentsPRO can use for fraud screening - Positively influence conversion/approval rate - Include optional fields required by your specific flow

Constants (fallback fields)

Constants are static values that Corefy can send to paymentsPRO 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 -> the field is simply omitted from the request to paymentsPRO (no hardcoded placeholder is sent in its place)

Currently available constants (constant -> Corefy API field)

FIRST_NAME -> customer.name (first part) - the cardholder's first name from the card is tried before this Constant
LAST_NAME -> customer.name (last part) - the cardholder's last name from the card is tried before this Constant
EMAIL -> customer.email
PHONE -> customer.phone
CUSTOMER_ADDRESS -> customer.address.full_address (or .street)
CUSTOMER_CITY -> customer.address.city
CUSTOMER_STATE -> customer.address.region
CUSTOMER_COUNTRY -> customer.address.country
CUSTOMER_POST_CODE -> customer.address.post_code

Options

ignore_callback -> optional, boolean - for cascading setups, excludes this connection from using the asynchronous callback to finalize payments; instead Corefy finalizes exclusively through an active status request (reconciliation).

Refunds

paymentsPRO does not support refunds through Corefy.

Recurring

paymentsPRO does not support saving/charging a token through Corefy.

Additional info

Active reconciliation is always used - Corefy confirms a payment's final status with an active status request to paymentsPRO, in addition to the asynchronous callback; a payment identifier (original id) is required for this. The incoming callback itself only carries a payment identifier, not a final status - it is a trigger for the active status check rather than a source of truth on its own.
No refunds, no recurring - neither capability is implemented for this connector.
Card networks - only Visa and Mastercard are supported; other networks are not processed.
3-D Secure - when required by the issuer, paymentsPRO returns a redirect URL and Corefy drives the 3DS/redirect flow for you.
Connection test - when you connect the account, Corefy verifies your credentials by sending a status request for a dummy payment ID and checking for the expected "invalid payment id" response from paymentsPRO - no real transaction is created.

FAQ / Troubleshooting

Invalid credentials / auth error -> verify the Header token and Auth key match the selected environment (Test Mode)
Payment stuck pending -> paymentsPRO may not have finalized the transaction yet; Corefy keeps checking status via active reconciliation
Card declined for a non-Visa/Mastercard network -> paymentsPRO only supports Visa and Mastercard
Refund request fails -> paymentsPRO does not support refunds through Corefy
Payments not finalizing via callback in a cascading setup -> enable the ignore_callback Option so finalization relies solely on active reconciliation

Question

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