PayLink (TAS LINK)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Merchant (Terminal ID) -> merchant_id
• Private Key -> private_key
• Google Pay Merchant ID -> google_pay_mid -> (optional, only if you enable the google_pay feature)
• Send Merchant URL -> send_merchant_url -> (optional) if enabled, your Commerce website URL is included in the order description sent to PayLink
• Currency / Features -> choose values available for your account (Payment Card, Google Pay, Apple Pay, Masterpass)
• Payment mode -> payment_mode -> (optional) E-commerce (default) or C2A - set per feature, see the Options section below
• FPTTI -> fptti -> (optional) 3-character transaction type indicator, used in C2A mode for Mastercard

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. Apple Pay, Google Pay, and Masterpass are all supported on this same connection, gated by the corresponding Dashboard features.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8afec793-9b41-4dc4-b281-c76cc54ffb89",
      "service": "payment_card_uah_hpp",
      "currency": "UAH",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "06fa1ea9-8a5b-4dbc-b67b-6236b3b9af3d",
      "service": "payment_card_uah_hpp",
      "currency": "UAH",
      "amount": 10.04,
      "customer": {
        "reference_id": "cus_123",
        "phone": "+380680786663",
        "email": "johnwick@example.com",
        "address": {
          "country": "UA",
          "city": "Kyiv",
          "full_address": "95 Richmond Road",
          "post_code": "01001",
          "region": "Kyiv"
        }
      }
    }
  }
}

Extended request (MAX)

Why add extra fields (typical reasons): - PayLink uses customer.address/customer.phone/customer.email to fill the 3DS billing fields (billAddrCity, billAddrCountry, billAddrLine1, billAddrPostCode, billAddrState, billMobilePhone, billEmail) - providing them can reduce 3DS friction - 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 (5):

• payment_mode - switches the connection between E-commerce (regular purchase) and C2A (Card2Account transfer) processing.
• fptti - transaction type indicator sent to PayLink in C2A requests (required for Mastercard).
• enable_fallback_on_browser_info - fills in missing 3DS browser-fingerprint fields from Constants instead of sending them empty.
• require_card_data_on_google_pay - Google Pay only; keeps a successful Google Pay payment Pending until card data (PAN) is returned so Corefy can store it.
• use_new_description - builds the order description PayLink receives from the payment's purpose metadata and the customer's tax ID/passport number, instead of the default auto-generated description.

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 -> PayLink receives an empty value for that field

Currently available constants (constant -> Corefy API field)

• NAME -> fallback for the cardholder name on the 3DS billing form
• CITY -> customer.address.city
• COUNTRY -> customer.address.country
• ADDRESS -> customer.address.full_address
• POST_CODE -> customer.address.post_code
• STATE -> customer.address.region (used for Sale/Auth)
• STATE_FOR_VERIFY -> customer.address.region (used specifically for the 3DS enrollment check step)
• PHONE -> customer.phone
• EMAIL -> customer.email
• MERCHANT_URL -> fallback website URL, only used when Send Merchant URL is enabled and no Commerce website URL is available

Eleven additional BROWSER_* constants (accept header, color depth, IP, short language, screen height/width, timezone offset, user agent, Java-enabled flag, window height/width) are also available - they are only used as fallback 3DS browser-fingerprint data when the enable_fallback_on_browser_info option above is enabled.

Refunds

PayLink supports partial refunds, but only one refund per payment - multiple (split) refunds against the same payment are not allowed. If the refund is processed on the same calendar day as the original sale (Kyiv timezone), Corefy automatically uses a void instead of a refund on PayLink's side - this is transparent to you.

Recurring

PayLink supports recurring (tokenized) charges. When a Sale is processed with the Corefy tokenize/save-card option enabled, PayLink returns a reusable token (recurring_sid) that Corefy stores and uses for subsequent recurring charges, without resubmitting card data - a genuine provider-side token flow, not just a Dashboard checkbox.

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields (provider -> Corefy)

• Merchant (Terminal ID) -> merchant
• Private Key -> private_key
• Account (Bank Account) -> account -> (exactly 14 characters; required unless P2P mode is enabled - do not use the full IBAN)
• P2P mode -> p2p -> (optional) enable to route payouts through PayLink's peer-to-peer network instead of a card-to-account transfer
• Merchant URL -> merchant_url -> (optional)

First request to Corefy API (MIN)

What it does: creates a payout-invoice for a card payout.

Payout - MIN

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "efbf0a2b-5590-42b7-b10b-94d49452147d",
      "service": "payment_card_uah",
      "currency": "UAH",
      "amount": 150,
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

Payout - MAX

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "58acf793-9b41-4dc4-b281-c76cc54ff230",
      "service": "payment_card_uah",
      "currency": "UAH",
      "amount": 150,
      "customer": {
        "reference_id": "33cc9165-6ab2-4cee-8d9a-10f05cddbb5a",
        "individual_tax_id": "1234567890"
      },
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

Extended request (MAX)

Why add extra fields (typical reasons): - customer.individual_tax_id is only used when the use_new_description option is enabled on this account - Provide additional customer details for compliance/reconciliation - 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):

• use_new_description - same behavior as on the Payments flow above: builds the description PayLink receives from the payout's purpose metadata and the customer's tax ID/passport number.

Refunds

PayLink does not support refunds on Payouts.