PayPort

Connect Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• API Key
• API URL
• Currencies -> multi-select from the currencies enabled for your account
• Payment Flow -> Redirect or Invoice - picks which service-code suffix you'll use (_hpp for Redirect, _invoice for Invoice) - see Additional info for what each one means
• Account Type -> Receipt or No Receipt
• Currency to Currency -> enable to allow PayPort to match a payment against a different currency than requested
• Exact Currency -> enable to require an exact currency match instead
• Generate Random Data -> enable to have Corefy auto-generate a random customer identity whenever one isn't provided (see the note on the MAX example below)
• Payment System Filter -> enable to restrict routing to the specific local payment system implied by the service/method you connect
• Delayed Fail -> enable to hold a failed status as pending for a grace period before reporting it as failed (paired with the delay_time_in_minutes Option below)
• Test Mode -> (enable if you are using sandbox credentials)

First request to Corefy API (MIN)

What it does: creates a payment-invoice. On a Redirect-flow service, this returns a redirect link to PayPort's hosted payment page.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8e3dbbb0-17af-4c9a-bedb-93bdac6900a2",
      "service": "card_transfer_rub_hpp",
      "currency": "RUB",
      "amount": 1000
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "card_transfer_rub_hpp",
      "currency": "RUB",
      "amount": 1000,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567"
      }
    }
  }
}

customer is optional. For most services, only customer.name/customer.email are forwarded; customer.phone is also forwarded for "by mobile" methods and whenever Account Type is set to No Receipt. If Generate Random Data is enabled on the account and you don't send customer, Corefy invents a random name/email (and phone, where relevant) rather than leaving the fields empty or failing the request - this is different from a fixed placeholder, a new random identity is generated per request.

Payment - MIN (Invoice flow, UPI India)

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "3c6d2f8e-8a2a-4e7a-9b1a-2f6a7b9c0d1e",
      "service": "upi_inr_invoice",
      "currency": "INR",
      "amount": 500
    }
  }
}

This connector covers over 80 service/currency combinations across CIS, the Middle East, South Asia, Southeast Asia, and Latin America, each in both _hpp and _invoice variants - see Additional info for the full breakdown.

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)

• delay_time_in_minutes - how long a failed status is held as pending before being reported, when Delayed Fail is enabled on the account.
• cut_amounts - truncates PayPort's reported amount instead of rounding it.

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. Available only for a specific subset of services (most CIS/Middle East/South Asia/Southeast Asia/Latin America methods - see Additional info for a full list of which).

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)

• EMAIL -> customer.email

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• API Key
• API URL
• Currencies -> multi-select from the currencies enabled for your account
• Account Type -> Receipt or No Receipt
• Currency to Currency / Exact Currency / Generate Random Data / Payment System Filter -> same meaning as on the Merchant account (Payments) above
• Merchant Expense -> enable if you (the merchant), rather than the recipient, cover the payout's transaction fee
• Local Methods Expected -> enable if you expect this account to route to local payout methods specifically
• Test Mode -> (enable if you are using sandbox credentials)

First request to Corefy API (MIN)

What it does: creates a payout-invoice and sends funds to a card, bank account, or local payout method, matched against an available PayPort "ad".

Payout - MIN (card)

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "0dde9e79-2c64-4703-adaf-93d710633401",
      "service": "payment_card_rub",
      "currency": "RUB",
      "amount": 1000,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith"
      },
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

Payout - MIN (IMPS, India)

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "3c6d2f8e-8a2a-4e7a-9b1a-2f6a7b9c0d1e",
      "service": "imps_inr",
      "currency": "INR",
      "amount": 500,
      "customer": {
        "reference_id": "cus_123"
      },
      "fields": {
        "account_number": "110147429820",
        "beneficiary_full_name": "John Smith",
        "bank_name": "Canara Bank",
        "ifsc": "CNRB0004425"
      }
    }
  }
}

fields.card_number is required for card payouts. IMPS/RTGS/NEFT (India) use bank-account fields instead: fields.account_number, fields.beneficiary_full_name, fields.bank_name, fields.ifsc. UPI/cash methods, and bank transfers in KRW/INR, instead use customer.name/customer.email/customer.phone plus fields.pan_number where relevant (India's PAN tax ID). This connector covers around 40 payout service/currency combinations - see Additional info for the full list.

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 (1)

• payout_round_up - rounds a payout amount with decimals up before sending it to PayPort.

No Constants are configured for this flow.