Skip to content

Logo

Payzln

Supports in this guide: Payments

Provider website: payzln.com


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

  1. Get your credentials (from Payzln)
  2. Connect in Dashboard
  3. Send an API request
  4. Configure Constants (optional, recommended)

Prerequisites: get from Payzln

Get the following values for your Payzln account:

  • App ID -> Corefy field app_id -> where to find: Payzln backoffice / issued by Payzln manager
  • App Secret -> Corefy field app_secret -> where to find: Payzln backoffice / issued by Payzln manager
  • Test mode -> Corefy field test_mode -> whether to send requests to Payzln's sandbox or live environment

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

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields

  • App ID
  • App Secret
  • Test mode -> true/false

Success

You have connected Payzln Provider account!


First request to Corefy API (MIN)

What it does: creates a payment-invoice for the upi_inr_hpp service (UPI collection, INR only).

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8afec793-9b41-4dc4-b281-c76cc54ffb89",
      "service": "upi_inr_hpp",
      "currency": "INR",
      "amount": 34,
      "customer": {
        "reference_id": "cus_123"
      }
    }
  }
}
This MIN request is valid only if the referenced Corefy Customer (cus_123) already has a phone number saved, or the PHONE constant is configured for this service (see Constants below) - Payzln requires a mobile number to create the UPI collection request.

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8fef37d2-31a8-4309-94ae-ce83cacff4f3",
      "service": "upi_inr_hpp",
      "currency": "INR",
      "amount": 34,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Wick",
        "email": "johnwick@gmail.com",
        "phone": "9876543210"
      }
    }
  }
}


Extended request (MAX)

Why add extra fields (typical reasons):

  • Provide the customer's mobile number directly in the request instead of relying on a saved Customer profile or a Constant
  • Provide additional customer details for compliance/reconciliation
  • Positively influence conversion rate

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.

So, if a field is missing in the API request, Corefy can take the value from the configured Constants.

After the successful connection, fill in constants for the upi_inr_hpp route in the editing menu.

Priority (predictable rule):

  1. If a value is present in the request -> Corefy uses the request value
  2. Else if the constant is set and value isn't present in the request -> Corefy uses the constant
  3. Else -> the field is sent empty, and Payzln may reject the request (this applies in particular to the mobile number - see note above)

Currently available constants (constant -> Corefy API field)

  • NAME -> customer.name
  • EMAIL -> customer.email
  • PHONE -> customer.phone (must be a 10-digit mobile number, no country code)

Refunds

Not supported. The Payzln connector does not implement a refund flow.

Recurring

Not supported. The Payzln connector does not implement recurring/tokenized payments.


Additional info

  1. Payment flow is redirect-based (HPP): after the payment is created, the customer is redirected to Payzln's hosted page to complete the payment via UPI intent or UPI QR.
  2. The connector supports active reconciliation - Corefy can query Payzln's transaction status endpoint directly to confirm a payment's outcome, in addition to processing Payzln's callback notifications.
  3. Callback notifications from Payzln are signed (HMAC SHA-256, using your App Secret); Corefy verifies the signature before processing a notification.
  4. Currently only one service is available: upi_inr_hpp (UPI payment method, INR currency only).
  5. The Payzln API base URL (sandbox/live) is determined automatically by the Test mode setting and is not a separate credential field.

FAQ / Troubleshooting

  • Payment request fails or is rejected -> confirm the customer's mobile number is present - either saved on the Corefy Customer profile, passed directly in the request, or configured as the PHONE constant.
  • Invalid credentials / auth error -> verify App ID and App Secret match the environment selected by Test mode (sandbox vs production).
  • Does Payzln support refunds or recurring payments? -> No, neither is currently supported by this connector.
  • Which currencies/methods are supported? -> Only UPI payments in INR via the upi_inr_hpp service.
  • Not sure which fields to fill in? -> ask your Corefy account manager.

Question

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