PayWings

Supports in this guide: Payments

Provider website: paywings.com

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

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

Prerequisites: get from PayWings

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

Login -> Corefy field login.
Password -> Corefy field password.
SSL certificate -> Corefy field ssl_certificate -> optional, a file; upload it together with the SSL Password to authenticate requests with a client certificate.
SSL Password -> Corefy field ssl_password -> optional, required only if an SSL certificate is uploaded.
API URL -> Corefy field api_url -> optional, overrides the default endpoint; only needed if PayWings issues you a dedicated URL.

KZT only.

Payments processing (connect H2H Merchant account, create payment-invoice)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

Login
Password
SSL certificate (optional)
SSL Password (optional)
API URL (optional)
Save token -> (saves PayWings's own order id for this transaction server-side; see Additional info)
Test Mode -> (enable if you are using sandbox credentials)

Choose Currency and Features. You can set these parameters according to available currencies and features for your PayWings account, but it is necessary to check details of the connection with your Corefy account manager.

Success

You have connected PayWings 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. PayWings always requires the CVV - non-CVV payments are not supported.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "a7a12a3e-32bb-4683-997e-e063514c882e",
      "service": "payment_card_kzt_hpp",
      "currency": "KZT",
      "amount": 1001
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "08f5e97c-1170-4bda-9625-3bde3c6dcd20",
      "service": "payment_card_kzt_hpp",
      "currency": "KZT",
      "amount": 1001,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "address": {
          "country": "KZ"
        }
      }
    }
  }
}

Important

Of all the customer/billing fields, only customer.email and customer.address.country actually reach PayWings - customer.phone, and the rest of customer.address (city/region/zip/full address), are accepted by Corefy but are not forwarded to PayWings for this connector. customer.name is not sent either, unless the use_customer_name_as_card_holder option (see Options) is enabled, in which case it replaces the cardholder name taken from the card itself.

Extended request (MAX)

Why add extra fields (typical reasons): - Provide the customer's email/country for compliance or PayWings-side reporting - Force the cardholder name to follow the customer's own name - 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 (5)

always_force3d - forces 3D Secure on every transaction
disable_secure3d20_return_url - omits the 3DS2 return URL from the request
use_customer_name_as_card_holder - sends the customer's name as the cardholder name instead of the name entered on the card
browser3ds_method - collects the 3DS2 "method" step via the customer's browser (iframe) instead of server-side
pending_on_validation_failure - changes how a validation failure during 3DS completion is reported

always_force3d

What it does: forces 3D Secure authentication on every transaction, regardless of how it would otherwise be routed.

When to use: if you want every PayWings payment to go through 3DS.

Default: "false"