Procard

Supports in this guide: Payments

Provider website: procard.ua

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

1. Get your credentials (from Procard)
2. Connect in Dashboard
3. Send an API request

Prerequisites: get from Procard

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

• Merchant ID -> Corefy field merchant_id.
• Merchant Key -> Corefy field merchant_key - optional at connect time, but needed for the 3DS v2 flow (it is used to sign those requests). If Procard did not give you a separate Merchant Key, it matches the password of your certificate file.
• Private Key / Certificate / CA (Client) Certificate -> Corefy fields key / cert / ca_cert - optional at connect time, but required for a secure (mutual TLS) connection in production; see conversion note below.
• Bank Account (IBAN) -> Corefy field iban - optional; the account that receives funds, added into the order description sent to Procard.

Procard issues credentials as a merchant ID, a merchant key, and a certificate file with a password, in the .p12 format. Convert the .p12 file into separate .pem files (Private Key, Certificate, Client/CA Certificate) before uploading them.

# the Private key
openssl pkcs12 -in <file.p12> -out filekey.pem -nocerts -nodes
# the Certificate
openssl pkcs12 -in <file.p12> -out filecert.pem -clcerts -nodes -nokeys
# the Client/CA Certificate
openssl pkcs12 -in <file.p12> -out fileCA.pem -cacerts -nodes -nokeys

Currencies: UAH, EUR.

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

Additional info

1. Active reconciliation is available - if a purchase or completion call to Procard times out or fails to connect, Corefy marks the payment for reconciliation instead of failing it outright, and an active status request can resolve the final outcome afterwards.
2. No recurring - this connector does not support saving/charging a token through Corefy.
3. No Options or Constants are configured for this connector.
4. Supports both 3DS v1 (PaReq/PaRes) and 3DS v2 (AReq/CReq) authentication flows, selected automatically per transaction.
5. In addition to standard card purchases, the connector also supports a card-to-account (P2P) transfer order type internally.
6. If you don't upload the Private Key / Certificate / CA Certificate files, Corefy disables SSL certificate verification when calling Procard's API - upload all three for a secure connection in production.
7. If the customer's IP address is a private-use (internal) address at the moment the 3DS challenge is completed, a fixed fallback IP is sent to Procard instead of the private one.
8. Dynamic Descriptor builds the order description from your own Corefy merchant profile (company name, MCC, city, address) - not from customer-supplied data.

FAQ / Troubleshooting

• Invalid credentials / auth error -> verify the Merchant ID, Merchant Key, and Test/Live mode match the selected environment
• Connection fails with SSL/certificate errors -> upload the converted .pem Private Key, Certificate, and CA Certificate files (see the conversion commands above)
• Refund rejected -> only one partial or full refund is allowed per payment; a second refund on the same payment is not supported
• 3DS challenge / enrollment issues -> Procard decides between 3DS v1 and 3DS v2 automatically; make sure your checkout integration forwards the browser/device data Corefy collects
• Payment stuck pending -> active reconciliation will resolve it once Corefy can reach Procard again