DragonTech

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Merchant ID
• Secret key
• Payment provider account (PPA)

First request to Corefy API (MIN)

What it does: creates a payment-invoice and redirects the customer to DragonTech's hosted checkout.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "cf58dbc1-5cf8-4622-8695-ef0d9595efae",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 27
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "4f9bd168-3ad0-4177-8ba9-7f5997927564",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 32,
      "customer": {
        "reference_id": "8c5a4832-45fc-49ad-bb8f-f38a4c46c685",
        "name": "John Wick",
        "email": "test@test.com",
        "phone": "445556667788",
        "date_of_birth": "2000-02-01",
        "address": {
          "country": "AW",
          "city": "City",
          "street": "Street",
          "post_code": "Postcode"
        },
        "metadata": {
          "client_ip": "3.65.180.235"
        }
      },
      "metadata": {
        "additional_fields": {}
      }
    }
  }
}

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

• finalize_on_fail -> optional, boolean - in rare cases a payment can change from a failed status to another status; enabling this option treats a failed status as final and ignores any later status change.

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)

• CUSTOMER_ID -> customer.reference_id
• FIRST_NAME -> customer.name (first part)
• LAST_NAME -> customer.name (second part)
• COUNTRY -> customer.address.country
• CITY -> customer.address.city
• FULL_ADDRESS -> customer.address.full_address
• POST_CODE -> customer.address.post_code
• EMAIL -> customer.email
• PHONE -> customer.phone
• BIRTH_DATE -> customer.date_of_birth
• IP -> customer.metadata.client_ip

Refunds

DragonTech does not support refunds.