Skip to content

Logo

Transfr

Supports in this guide: Payments

Provider website: transfr.io


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

  1. Get your credentials (from Transfr)
  2. Connect in Dashboard
  3. Send an API request

Prerequisites: get from Transfr

Send a connection request at transfr.io or contact your Transfr account manager directly to get your account verified and receive the following credentials.

  • API Key -> Corefy field api_key.

Available currencies depend on the routes configured for your account.


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

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • API Key
  • Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected Transfr 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.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "5cc69025-3515-47c4-b70a-22718826e4ea",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 2
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6dd7a136-4626-48d5-c3cd-33829937f5fb",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 2,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Doe",
        "email": "john@example.com",
        "phone": "+380999999999",
        "address": {
          "full_address": "Main street 1",
          "country": "GB",
          "region": "London",
          "city": "London",
          "post_code": "31000"
        }
      }
    }
  }
}

Important

customer.name is split into first/last name; the card's own embossed cardholder name is also sent separately as card_details.cardholder_name.


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.

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)

  • FIRST_NAME -> customer.name (first part)
  • LAST_NAME -> customer.name (second part)
  • EMAIL -> customer.email
  • PHONE -> customer.phone
  • FULL_ADDRESS -> customer.address.full_address
  • CITY -> customer.address.city
  • POST_CODE -> customer.address.post_code
  • REGION -> customer.address.region
  • COUNTRY -> customer.address.country

Refunds

Transfr does not support refunds.


Additional info

  1. Active reconciliation is available - both the asynchronous callback and an active status request can finalize the payment.
  2. No recurring - this connector does not support saving/charging a token through Corefy.
  3. No Options are configured for this connector.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify the API Key for the selected environment (test_mode)
  • Currency or service is not supported -> confirm allowed currencies/features in your Transfr account and in Corefy
  • Refund fails -> Transfr does not support refunds through Corefy

Question

Still looking for help connecting your Transfr account? Please contact our support team!