Payes

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Shop ID -> shop_id
• Public key -> public_key
• Secret key -> secret_key
• Test mode -> test_mode
• 3-D Secure mode -> three_ds_mode (Simple / Advanced)

Additionally, choose Currency and Features according to what is enabled for your Payes account.

First request to Corefy API (MIN)

What it does: creates a payment-invoice.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8afec793-9b41-4dc4-b281-c76cc54ffb89",
      "service": "payment_card_eur",
      "currency": "EUR",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "06fa1ea9-8a5b-4dbc-b67b-6236b3b9af3d",
      "service": "payment_card_eur",
      "currency": "EUR",
      "amount": 10.04,
      "customer": {
        "reference_id": "cus_123",
        "email": "sss@gmail.com"
      }
    }
  }
}

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

Options

Options are configured on the Corefy side and affect how Corefy builds provider requests or processes responses.

Currently available options (2)

• ignore_callback - ignores incoming provider callbacks for this account
• send_customer_data - sends customer billing details (name, country, city, state, zip, address) with each request

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.

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 -> Corefy sends its own built-in placeholder value (see note below)

Currently available constants (constant -> Corefy API field)

• IP -> client IP address
• DESCRIPTION -> payment description
• LANG -> language
• EMAIL -> customer.email
• REASON -> refund reason
• COUNTRY -> customer.address.country (sent only when send_customer_data is enabled)
• CITY -> customer.address.city (sent only when send_customer_data is enabled)
• STATE -> customer.address.region (sent only when send_customer_data is enabled)
• ZIP -> customer.address.postCode (sent only when send_customer_data is enabled)
• ADDRESS -> customer.address.fullAddress (sent only when send_customer_data is enabled)

Refunds

Refunds are supported for the H2H Merchant account:

• Partial refunds are allowed.
• Only a single refund per transaction is allowed (multiple/split refunds on the same transaction are not supported).
• The original transaction ID is always required.
• The refund reason sent to Payes comes from your request description, or falls back to the REASON constant (default return of goods) if not provided.

Reconciliation

Active reconciliation is supported: Corefy can query Payes directly for the current status of a transaction, rather than relying only on callbacks.

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields (provider -> Corefy)

• Shop ID -> shop_id
• Secret key -> secret_key
• Public key -> public_key
• Test mode -> test_mode
• Live URL (optional) -> live_url - only needed if your account manager gave you a custom API host; otherwise the default production host is used.

First request to Corefy API (MIN)

What it does: creates a payment-invoice.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "eae08d28-1a7a-407f-ab4d-2c8275ca7964",
      "service": "upi_inr_hpp",
      "currency": "INR",
      "amount": 100
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "58acf793-9b41-4dc4-b281-c76cc54ff230",
      "service": "upi_inr_hpp",
      "currency": "INR",
      "amount": 100,
      "customer": {
        "reference_id": "33cc9165-6ab2-4cee-8d9a-10f05cddbb5a",
        "first_name": "John",
        "last_name": "Doe",
        "email": "sss@gmail.com",
        "phone": "380663031389",
        "address": {
          "country": "IN"
        }
      }
    }
  }
}

This flow covers the hosted-page and local-method side of Payes (for example, UPI payments in India); available services/currencies depend on what is enabled for your account - confirm the exact list with your account manager.

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

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. Unlike the H2H Merchant account, the Provider account has no built-in placeholder values - if a field is missing from both your request and Constants, it is simply left blank.

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 left blank

Currently available constants (constant -> Corefy API field)

• LANGUAGE -> language
• FIRST_NAME -> customer.first_name
• LAST_NAME -> customer.last_name
• EMAIL -> customer.email
• PHONE -> customer.phone
• COUNTRY -> customer.address.country

Refunds

Refunds are not available through the Provider account. If you need refund capability, use the H2H Merchant account instead.

Reconciliation

Active reconciliation is supported: Corefy can query Payes directly for the current status of a transaction, rather than relying only on callbacks.