Payments Trust

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Account ID
• API Key
• Key for Callback (optional)
• API URL (optional)
• Send Metadata (optional)
• Test Mode -> (enable if you are using sandbox credentials)

Choose Currency / Features; check with your Corefy account manager which are enabled for your 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. Apple Pay and Google Pay are supported on the same connection, with token decryption handled by Corefy. Payments Trust may return a 3D Secure redirect, or an OTP (one-time password) confirmation step, depending on the card and account setup.

Payment - MIN

POST /api/payment-invoices

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

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "address": {
          "country": "FR",
          "city": "Paris",
          "full_address": "1 Main street",
          "post_code": "75000"
        }
      }
    }
  }
}

customer is entirely optional - anything you don't send falls back to the Constants below, or is simply left blank on Payments Trust's side.

Available currencies: UAH, RUB, EUR, USD.

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 - 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.
• save_provider_instant_token -> optional, boolean - saves a reusable token on a successful sale, for later recurring/merchant-initiated charges.
• generate_random_customer_data -> optional, boolean - replaces the entire customer block with a fully random one before sending it to Payments Trust; use only if your flow genuinely has no real customer data to send.
• transliterate_customer_data -> optional, boolean - transliterates customer fields (e.g. Cyrillic) to Latin before sending.
• transliterate_card_holder -> optional, boolean - transliterates the cardholder name to Latin before sending.
• set_description -> optional, boolean - forwards a transaction descriptor as the sale's description, if one is set.
• duplicate_original_resolution -> optional, boolean - advanced reconciliation setting; ask your account manager before enabling.

Constants (fallback fields)

Constants are static values that Corefy can send to Payments Trust 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 -> Corefy API field)

• EMAIL -> customer.email
• PHONE -> customer.phone
• COUNTRY -> customer.address.country
• CITY -> customer.address.city
• ADDRESS -> customer.address.full_address
• POST_CODE -> customer.address.post_code
• METADATA_KEY / METADATA_VALUE -> adds one fixed metadata key-value pair to every sale, if Send Metadata is enabled.
• BROWSER_SCREEN_WIDTH, BROWSER_SCREEN_HEIGHT, BROWSER_COLOR_DEPTH, BROWSER_LANGUAGE, BROWSER_JAVA_ENABLED, BROWSER_ACCEPT_HEADER, BROWSER_USER_AGENT, BROWSER_IP, BROWSER_TZ -> fallback browser/device fingerprint values used for 3D Secure, if Corefy's checkout doesn't already collect them.

Refunds

This connector does not support refunds through Corefy.

Recurring

Enabling save_provider_instant_token (or sending options.tokenize in the request) saves a reusable token on a successful sale, which can later be charged again without card data through Corefy's recurring/merchant-initiated-transaction flow.

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Commerce ID
• API Key
• Secret Key for Callback
• API URL (optional)
• Send Metadata (optional)
• Test Mode -> (enable if you are using sandbox credentials)

First request to Corefy API (MIN)

What it does: creates a payment-invoice and redirects the customer to a Payments Trust-hosted page to complete a card payment.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "0dde9e79-2c64-4703-adaf-93d710633401",
      "service": "payment_card_eur",
      "currency": "EUR",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "3c6d2f8e-8a2a-4e7a-9b1a-2f6a7b9c0d1e",
      "service": "payment_card_eur",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com"
      }
    }
  }
}

customer is entirely optional for this flow.

Routes/currencies and the exact service code are configured per account with Payments Trust rather than fixed in Corefy - confirm the available service code(s) with your account manager.

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 connector does not support refunds through Corefy.

Recurring

This flow does not support saving/charging a token through Corefy.

Connect Provider account in Corefy Dashboard

Uses the same Provider account connection as the Payments flow above - no separate connect step.

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": "4d5e6f7a-8b9c-4d0e-8f13-4a5b6c7d8e9f",
      "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": "5e6f7a8b-9c0d-4e1f-9023-5b6c7d8e9f0a",
      "service": "payment_card_eur",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com"
      },
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

customer is entirely optional and only forwarded as recipient details.

Routes/currencies and the exact service code are configured per account with Payments Trust rather than fixed in Corefy - confirm the available service code(s) with your account manager.

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

• send_description -> optional, boolean - forwards the payout's description text to Payments Trust.
• allow_conversion -> optional, boolean - by default, a payout route is only available when its settlement currency exactly matches the request currency; enable this to let Payments Trust accept a different request currency and convert it to your account's settlement currency.

No Constants are configured for this flow.