TrustPay (Finby)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Project ID
• API key
• Secret key
• Customer data required (optional) -> rejects a payment before it reaches TrustPay if customer.email is missing, instead of sending it without an email.
• Save browser data (optional)
• Currency / Features -> choose values available for your account
• Test Mode -> (enable if you are using sandbox credentials)

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. TrustPay may return a 3D Secure challenge redirect depending on the card.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "1a2b3c4d-5e6f-4a7b-8c91-2d3e4f5a6b7c",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "2b3c4d5e-6f7a-4b8c-8d02-3e4f5a6b7c8d",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "test@example.com",
        "address": {
          "full_address": "Main street 1",
          "city": "Bratislava",
          "country": "SK",
          "post_code": "83103"
        }
      }
    }
  }
}

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

• customer_data_required -> optional, boolean - rejects the payment before it reaches TrustPay if customer.email is missing, instead of sending the request without it.
• save_browser_data -> optional, boolean - requires full browser fingerprint data (user agent, screen size, timezone, etc.) to be present, rejecting the payment beforehand if it's missing.
• save_instant_token -> account-level setting that enables saving a token for recurring charges.

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 -> Corefy API field)

• CITY -> customer.address.city
• STREET -> customer.address.full_address
• COUNTRY -> customer.address.country
• POST_CODE -> customer.address.post_code

Refunds

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

Recurring

TrustPay supports saving and charging a card token through Corefy (enabled via the account-level save_instant_token setting).