Skip to content

Logo

FONDY

FONDY is simplifying global payments for small and medium-sized businesses looking for an easy and affordable way to accept online payments in a variety of ways including cards, online banking and digital wallets such as Apple Pay.

Supports in this guide: Payments

Provider website: fondy.eu

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

  1. Get your credentials (from FONDY)
  2. (optional) Get your Apple Pay registration
  3. Connect in Dashboard
  4. Send an API request

Prerequisites: get from FONDY

Register at the FONDY portal and get the following credentials from 'Merchant settings' -> 'Technical settings'.

  • Merchant ID -> Corefy field merchant_id.
  • Password -> Corefy field password.

Optional: get Apple Pay registration

If you need to connect Apple Pay with FONDY, get your Apple Merchant ID by completing the requirements at the Apple Developer site.

Then generate the Apple Pay certificate yourself, or apply to FONDY or Corefy support for help:

  1. Generate keys and CSRs (Certificate Signing Requests): ??? example "Example console commands (macOS)" 
    openssl genrsa -out merchant.key 2048
openssl ecparam -out apple_pay.key -name prime256v1 -genkey
# Apple Pay Merchant Identity Certificate Request
openssl req -new -key merchant.key -out merchant.csr
# Apple Pay Payment Processing Certificate Request
openssl req -new -sha256 -key apple_pay.key -nodes -out apple_pay.csr
  2. Use the CSR files to generate certificates at developer.apple.com.

  3. Convert the resulting CRT certificates to .pem and .p12: ??? example "Example console commands (macOS)" 

    # DER to PEM
openssl x509 -inform DER -outform PEM -text -in merchant.cer -out merchant.pem
openssl x509 -inform DER -outform PEM -text -in apple_pay.cer -out apple_pay.pem

# PEM to P12
openssl pkcs12 -export -out apple_pay.p12 -inkey apple_pay.key -in apple_pay.pem
openssl pkcs12 -export -out merchant.p12 -inkey merchant.key -in merchant.pem

  4. Apple Merchant ID (optional) -> Corefy field apple_merchant_id.

  5. Apple Certificate (optional) -> Corefy field apple_cert -> uploaded as a file.
  6. Apple Certificate Key (optional) -> Corefy field apple_cert_key -> uploaded as a file.
  7. Apple Certificate password (optional) -> Corefy field apple_cert_password.

Note

You need to verify the domain from which you intend to call the Apple Pay API. Provide your Corefy HPP URL to your Apple Pay developer account manager, obtain a domain association file, and share it with your Corefy account manager. If you plan to use a white-label domain, determine the verification details with your account manager beforehand.

UAH, RUB, EUR, USD, GBP, PLN, CZK, CAD, AUD.

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

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

Open FONDY in the provider directory and press Connect at FONDY Provider Overview page in the New connection section.

Step 2 - Fill in fields and select settings

  • Merchant ID
  • Password
  • Apple Merchant ID (optional)
  • Apple Certificate / Certificate Key / Certificate password (optional)
  • Currency / Features -> choose values available for your account
  • Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected FONDY 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. Card and Apple Pay are supported on this same connection (Google Pay is not supported by this connector, despite being mentioned in some marketing material). FONDY may return a 3D Secure challenge as a second step, completed automatically behind this same request.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "1f2e3d4c-5b6a-4978-8c01-2d3e4f5a6b7c",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "2a3b4c5d-6e7f-4089-8d12-3e4f5a6b7c8d",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "description": "Order #12345",
      "customer": {
        "email": "test@example.com"
      }
    }
  }
}

Important

  • No Constants are configured for this connector. If customer.email is missing, a fixed placeholder email is sent to FONDY instead of leaving the field empty.
  • description is sent to FONDY as the order description; if missing, your own reference ID is used instead.

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

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

Additional info

  1. No asynchronous callback - FONDY does not send callbacks to Corefy for payments; statuses are updated via active status requests (reconciliation) only.
  2. No recurring - this connector does not support saving/charging a token through Corefy.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify the Merchant ID and Password for the selected environment (test_mode)
  • Apple Pay payment fails -> confirm your Apple Merchant ID, certificates, and domain verification are all correctly set up
  • Currency or service is not supported -> confirm allowed currencies/features in your FONDY account and in Corefy
  • Refund fails with multiple attempts -> only one refund per payment is allowed

Question

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