PayzEasy

Fast, secure payment processing with multi-currency support and seamless API integration.

Supports in this guide: Payments, Payouts

Provider website: payzeasy.com

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

Get your credentials (from PayzEasy)
Connect in Dashboard
Send an API request

Prerequisites: get from PayzEasy

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

Application ID -> Corefy field app_id.
Salt -> Corefy field salt - sent as a request header, not shown again after it's saved.
API URL -> Corefy field api_url - points at either your sandbox or production environment (for example https://uat-api.payzeasy.com).

Currently PayzEasy connects as a single Provider account and supports India-local methods only: UPI and IMPS for Payments, IMPS for Payouts - all in INR.

Payments processing (connect Provider account, create payment-invoice)

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

Application ID
Salt
API URL
Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected PayzEasy Provider account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice for a redirect (HPP) payment. PayzEasy returns a checkout URL; the customer completes UPI or IMPS payment there and is redirected back.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "2dea841e-8063-4b5b-b5c4-59d69d2bd96d",
      "service": "upi_inr_hpp",
      "currency": "INR",
      "amount": 100
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "2dea841e-8063-4b5b-b5c4-59d69d2bd96d",
      "service": "imps_inr_hpp",
      "currency": "INR",
      "amount": 100,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Doe",
        "email": "test@test.com",
        "phone": "+919876543210"
      }
    }
  }
}

Important

customer.reference_id, .name, .email and .phone are not enforced by Corefy, but PayzEasy uses them (as player_id/player_name/player_email/player_mobile) for its own KYC/compliance checks on UPI and IMPS - omitting them (and not setting the matching Constants below) risks a provider-side decline.
If customer.phone is sent without a leading +, Corefy adds it automatically before forwarding the request.
Only INR is supported, via the upi_inr_hpp (UPI) and imps_inr_hpp (IMPS) services.

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 -> the field is omitted from the request to PayzEasy (no hardcoded fallback value is sent)

Currently available constants (constant -> Corefy API field)

player_id -> customer.reference_id
player_name -> customer.name
player_email -> customer.email
player_phone -> customer.phone

Refunds

PayzEasy does not support refunds on this flow.

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

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 for an IMPS bank transfer payout in INR.

Payout - MIN

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "efbf0a2b-5590-42b7-b10b-94d49452147d",
      "service": "imps_inr",
      "currency": "INR",
      "amount": 150,
      "fields": {
        "account_number": "1222951828",
        "ifsc": "RATN0000161",
        "account_holder_full_name": "John Doe"
      }
    }
  }
}

Payout - MAX

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "efbf0a2b-5590-42b7-b10b-94d49452147d",
      "service": "imps_inr",
      "currency": "INR",
      "amount": 150,
      "customer": {
        "reference_id": "cus_123"
      },
      "fields": {
        "account_number": "1222951828",
        "ifsc": "RATN0000161",
        "account_holder_full_name": "John Doe"
      }
    }
  }
}

Important

fields.account_number, .ifsc and .account_holder_full_name are required - they are mapped to PayzEasy's own account_number, ifsc_code and account_holder fields.
customer.reference_id identifies the payout recipient on PayzEasy's side - if it's missing, Corefy falls back to the customer_id Constant if one is set; otherwise the field is omitted.
Only IMPS/INR is supported for Payouts.

Constants (fallback fields)

Currently available constants (constant -> Corefy API field)

customer_id -> customer.reference_id

Refunds

PayzEasy does not support refunds on Payouts.

Additional info

Active reconciliation is available on both Payments and Payouts - besides the asynchronous callback, Corefy can actively request the current status from PayzEasy to finalize a transaction.
No refunds - neither Payments nor Payouts support refunds through this connector.
No recurring - this connector does not support saving/charging a token through Corefy.
INR only - all Payments (UPI, IMPS) and Payouts (IMPS) are limited to Indian Rupee.
Constants never resolve to a hardcoded fake value - if a field is missing from the request and no matching Constant is set, Corefy simply omits it from the request to PayzEasy.

FAQ / Troubleshooting

Invalid credentials / auth error -> verify Application ID and Salt match the selected environment (test_mode) and the API URL
Payment declined by provider -> PayzEasy commonly requires customer KYC data (player_id/name/email/phone) for UPI and IMPS; make sure it's sent in the request or set as Constants
Payout stuck as Pending/Initializing -> PayzEasy reports these as non-final; wait for the callback or next reconciliation pass to pick up a final status
Payout fails with an invalid IFSC code -> double check fields.ifsc against the recipient's bank branch code
Payout fails with an amount limit error -> PayzEasy enforces its own payout amount limit; check it with your account manager

Question

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