Skip to content

Logo

PionPay

PION ensures high speed and conversion of acquired payments

Supports in this guide: Payments

Provider website: pion.finance

Note

This provider's public brand is PION; "PionPay" is the name used for its API/portal (e.g. api.pionpay.com) and is also this connector's code in Corefy - same provider, not a separate integration.

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

  1. Choose account type
  2. Get your credentials (from PionPay)
  3. Connect in Dashboard
  4. Send an API request

Choose account type

PionPay can be connected in different ways (depending on your needs):

  • If you do H2H card payments (card data sent directly) -> choose H2H Merchant account
  • If you do BLIK payments (Poland) via a hosted page -> choose Provider account

PionPay does not currently support payouts through Corefy. If you're not sure which one to use, confirm with your Corefy account manager.

Prerequisites: get from PionPay

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

For H2H Merchant account:

  • Public ID -> Corefy field public_id.
  • Secret Key -> Corefy field secret_key -> used to sign every request.

Note

There is no Test Mode toggle for the H2H Merchant account - PionPay exposes a single fixed endpoint, with no separate sandbox environment.

For Provider account:

  • Public ID -> Corefy field public_id.
  • API Secret -> Corefy field api_secret.
  • Account ID (optional) -> Corefy field account_id.
  • Payment Flow -> Corefy field payment_flow -> HPP or Invoice - choose HPP for the hosted-page flow described in this guide; ask your account manager if you're not sure which one your account uses.
Payments processing (connect H2H Merchant account, create payment-invoice)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • Public ID
  • Secret Key

Choose Currency / Features; check with your Corefy account manager which are enabled for your account.

Success

You have connected PionPay H2H Merchant account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice; card data itself is collected and submitted separately by Corefy's checkout/SDK layer, not as part of this request. PionPay may return a 3D Secure challenge redirect depending on the card.

Payment - MIN

POST /api/payment-invoices 

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

This connector also supports EUR, AZN, RUB, UZS.

Important

CVV is required for every currency except UZS - for UZS sales, a non-CVV sale is accepted; for any other currency, a sale without CVV is rejected.

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567"
      }
    }
  }
}

customer is entirely optional and is only used to enrich the sale.

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

No Constants are configured for this connector.

Options

  • ignore_callback -> optional, boolean - for cascading to work correctly, excludes finalizing the payment from the asynchronous callback; Corefy then relies only on an active status request (reconciliation) to finalize it.

Refunds

PionPay supports partial refunds, but only one refund per payment (no multiple partial refunds against the same payment).

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

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • Public ID
  • API Secret
  • Account ID (optional)
  • Payment Flow -> choose HPP

Success

You have connected PionPay Provider account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice and redirects the customer to a PionPay-hosted page to complete a BLIK payment (Poland only).

Payment - MIN

POST /api/payment-invoices 

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

Note

BLIK is currently the only method confirmed for this flow - card, Apple Pay, and Google Pay are not currently wired up here even though some directories list them for this provider; confirm with your account manager before relying on anything beyond BLIK.

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "blik_pln_hpp",
      "currency": "PLN",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com"
      }
    }
  }
}

customer is entirely optional - everything is only used to prefill the hosted form, it never blocks the sale.

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

No Options or Constants are configured for this flow.

Refunds

This flow does not support refunds - use the H2H Merchant account if you need refunds.

Additional info

  1. The H2H Merchant account uses a single fixed callback endpoint rather than a per-transaction URL; it's already set up on Corefy's side, nothing to configure in PionPay's own back-office.
  2. The Provider account uses automatic callback routing - Corefy generates the callback/return URL per transaction.
  3. No payouts - this connector does not support payouts through Corefy.

FAQ / Troubleshooting

  • Sale rejected for missing CVV -> CVV is required for every currency except UZS
  • Invalid credentials / auth error -> verify the credentials for the selected account type
  • Refund fails on the Provider account flow -> refunds aren't supported there - use the H2H Merchant account instead
  • Currency or service is not supported -> confirm allowed currencies/features in your PionPay account and in Corefy

Question

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