Procard.Pay

Supports in this guide: Payments, Payouts

Provider website: procard.ua

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

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

Choose account type

Procard.Pay can be connected in different ways (depending on your needs):

If you do direct card payments (H2H, no redirect) -> choose H2H Merchant account
If you do card payouts -> choose Provider account

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

Prerequisites: get from Procard.Pay

Contact your Procard.Pay account manager to get your account verified and receive the following credentials. H2H Merchant account and Provider account each use their own set of these same fields.

Merchant ID -> Corefy field merchant_id.
Private Key -> Corefy field private_key.
API URL -> Corefy field api_url -> Procard.Pay does not have fixed, separate sandbox/production hostnames - enter whichever URL Procard.Pay issued for the environment (test or production) you want to use.
Test Mode -> Corefy field test_mode -> marks the account as a test account in Corefy; it does not change which api_url is called.

UAH only.

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

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

Merchant ID
Private Key
API URL
Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected Procard.Pay 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. Procard.Pay may return a 3D Secure (v2) challenge depending on the card - the browser/device fingerprint data needed for the challenge is collected and forwarded automatically.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6be05631-8710-4b14-a369-1928a2b70eda",
      "service": "payment_card_uah_hpp",
      "currency": "UAH",
      "amount": 10
    }
  }
}

Important

No customer fields are used by this connector for Payments - only card data (collected separately by the checkout/SDK layer) is forwarded to Procard.Pay, so there is no separate MAX example.
Procard.Pay also accepts cards that don't require CVV entry: if the checkout layer doesn't collect a CVV, Corefy sends a fixed -1 placeholder in its place instead of leaving the field empty.

Options

use_reverse -> optional, boolean, default false - if enabled, a refund request is sent to Procard.Pay's reverse operation instead of its refund operation.

Refunds

Procard.Pay supports partial refunds, but only one refund per payment (no multiple partial refunds against the same payment).

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

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

Merchant ID
Private Key
API URL
Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected Procard.Pay Provider account!

First request to Corefy API (MIN)

What it does: creates a payout-invoice and sends funds directly to a card.

Payout - MIN

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "3c4d5e6f-7a8b-4c9d-8e02-3f4a5b6c7d8e",
      "service": "payment_card_uah",
      "currency": "UAH",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Doe"
      },
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

Important

fields.card_number is required.
customer.name is required for every payout - there is no MAX variant, since no other optional fields are read by this connector.
Your own merchant company name and tax/registration ID (taken automatically from your Corefy merchant profile) are sent as the sender details; your IBAN is also included if your merchant profile has one on file.

Refunds

Procard.Pay does not support refunds on Payouts.

Additional info

Active reconciliation: for Payments, both an asynchronous signed callback and an active status request can finalize a sale, and a refund's status can likewise be actively checked, not just reported through the callback. For Payouts, only an active status request is available - there is no asynchronous payout callback for this connector.
No recurring - this connector does not support saving/charging a token through Corefy on either flow.
Currency: UAH only, for both Payments and Payouts.
Payment callbacks are signed with an HMAC-SHA512 signature that Corefy verifies automatically; a callback with a missing or mismatched signature is rejected.

FAQ / Troubleshooting

Invalid credentials / auth error -> verify the Merchant ID and Private Key match the selected environment and account type (H2H Merchant vs Provider)
Connection test or request fails unexpectedly -> double-check the API URL matches the environment (test or production) you intend to use - Test Mode itself does not switch the endpoint
Payout request rejected -> make sure customer.name and fields.card_number are both sent; both are required
Second refund on the same payment is rejected -> Procard.Pay only allows one refund per payment, partial or full
Refund goes to the wrong endpoint -> check the use_reverse option; when enabled, refunds are routed to Procard.Pay's reverse operation instead of its refund operation

Question

Still looking for help connecting your Procard.Pay account? Please contact our support team!