Certus Finance

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Merchant ID
• Merchant account ID
• Merchant account key
• Username
• Password
• Test Mode -> (enable if you are using sandbox credentials)
• Currency / Features -> choose values available for your Certus Finance account

First request to Corefy API (MIN)

What it does: creates a payment-invoice. Certus Finance supports card payments via a hosted page, plus two India-only local methods that return requisites for the customer to pay with directly.

Pay-in services

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "f3a9c1d2-5b7e-4a3c-9c1e-8d2f6a4b7c91",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 100
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "0c8e4f2a-1d6b-4e7a-8c3f-2b9a7d5e6f10",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 100,
      "customer": {
        "reference_id": "cus_482910",
        "name": "John Doe",
        "email": "john@example.com",
        "phone": "+15551234567",
        "address": {
          "full_address": "123 Main street",
          "city": "Berlin",
          "post_code": "10115",
          "region": "BE",
          "country": "DE"
        }
      }
    }
  }
}

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

Certus Finance supports refunds, including partial refunds, but only one refund is allowed per payment - multiple/split refunds aren't supported.

Options

Options are configured on the Corefy side and affect how Corefy builds provider requests or processes responses. These apply to the card services (payment_card_eur_hpp/payment_card_inr_hpp/payment_card_usd_hpp) only.

Currently available options (1)

• is_three_ds_required - controls whether 3D Secure authentication is required for the card payment.

Constants (fallback fields)

Constants are static values that Corefy can send to the provider instead of dynamic data from your API request, when those fields are missing in the request. These apply to the card services only - the UPI/bank transfer services above don't use them.

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 -> provider may reject the request or apply its defaults (depends on provider)

Currently available constants (constant -> Corefy API field)

• FIRST_NAME -> customer.name
• LAST_NAME -> customer.name
• FULL_ADDRESS -> customer.address.full_address
• CITY -> customer.address.city
• POST_CODE -> customer.address.post_code
• STATE_CODE -> customer.address.region
• COUNTRY_CODE -> customer.address.country
• MOBILE -> customer.phone
• PHONE -> customer.phone
• EMAIL -> customer.email

Connect Provider account in Corefy Dashboard

Uses the same Provider account connected above - no separate connection step.

First request to Corefy API (MIN)

What it does: creates a payout-invoice. The recipient fields required in fields differ per currency/service.

Payout services and recipient fields

Payout - MIN (INR, UPI)

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "6b2d9a4e-3f7c-4a1b-9d6e-5c8a2f1b7e40",
      "service": "upi_inr",
      "currency": "INR",
      "amount": 500,
      "fields": {
        "vpa": "johndoe@upi"
      }
    }
  }
}

Payout - MAX (INR, bank transfer)

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "9d4f1c7a-6e2b-4c8d-a1f3-7b5e9c2d6a81",
      "service": "bank_transfer_inr",
      "currency": "INR",
      "amount": 500,
      "fields": {
        "bank_name": "HDFC Bank",
        "bank_code": "HDFC0001234",
        "beneficiary_full_name": "Rahul Sharma",
        "account_number": "1234567890",
        "account_type": "savings"
      }
    }
  }
}

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