WPayments

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Shop ID
• Public key
• Secret key
• 3DS mode -> simple or advanced
• Test Mode -> (enable if you are using sandbox credentials)
• Currency / Features -> choose values available for your account (RUB, EUR)

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. WPayments may return a 3D Secure challenge redirect depending on the card and your three_ds_mode setting.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "7a8b9c0d-1e2f-4a3b-8c04-7d8e9f0a1b2c",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8b9c0d1e-2f3a-4b4c-8d15-8e9f0a1b2c3d",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "description": "Order #123",
      "customer": {
        "reference_id": "cus_123",
        "email": "john@example.com",
        "address": {
          "country": "DE",
          "city": "Berlin",
          "state": "Berlin",
          "zip": "10115",
          "street": "Main street 1"
        }
      }
    }
  }
}

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

• ignore_callback -> optional, boolean - excludes WPayments's asynchronous callback from finalizing the payment; only an active status request (reconciliation) will do so. Useful for cascading, where you don't want an out-of-order callback changing the transaction status.
• send_customer_data -> optional, boolean - additionally sends customer details (name, email, address) collected from the request to WPayments.

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 -> provider may reject the request or apply its defaults (depends on provider)

Currently available constants (constant -> WPayments parameter)

• IP -> ip (client IP; falls back to the request user IP)
• DESCRIPTION -> description (payment description; falls back to the request description)
• LANG -> lang (customer's language)
• EMAIL -> email -> falls back to customer.email
• REASON -> reason (payment reason/purpose)
• COUNTRY -> country -> falls back to customer.address.country
• CITY -> city -> falls back to customer.address.city
• STATE -> state -> falls back to customer.address.state
• ZIP -> zip -> falls back to customer.address.zip
• ADDRESS -> address -> falls back to customer.address.street

Refunds

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

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Shop ID
• Secret key
• Public key
• Live URL (optional)
• 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 directly to a card.

Payout - MIN

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "9c0d1e2f-3a4b-4c5d-8e26-9f0a1b2c3d4e",
      "service": "payment_card_eur",
      "currency": "EUR",
      "amount": 10,
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

Payout - MAX

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "0d1e2f3a-4b5c-4d6e-8f37-0a1b2c3d4e5f",
      "service": "payment_card_eur",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Doe",
        "email": "john@example.com",
        "ip": "127.0.0.1"
      },
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

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.

After the successful connection, fill in constants for the necessary routes 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 -> Corefy uses the constant 3. Else -> Corefy falls back to a generic placeholder value (see above)

Currently available constants (constant -> WPayments parameter)

• DESCRIPTION -> description (payout description)
• CUSTOMER_NAME -> customer_name -> falls back from customer.name
• CUSTOMER_IP -> customer_ip -> falls back from customer.ip
• CUSTOMER_EMAIL -> customer_email -> falls back from customer.email

WPayments does not support refunds for payouts.