TransactWorld

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Partner ID
• Username
• Secret Key
• Member ID
• Terminal ID
• 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. TransactWorld attempts a direct card charge and, if it decides a 3D Secure challenge is needed, returns a redirect for the customer to complete it.

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",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "address": {
          "country": "FR",
          "region": "Paris",
          "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 (city/state/country/post code/street/email/phone/IP), or is simply left blank on TransactWorld's side.

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.

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)

• REFERENCE_ID -> customer.reference_id
• COUNTRY -> customer.address.country
• STATE -> customer.address.region
• CITY -> customer.address.city
• STREET -> customer.address.full_address
• POST_CODE -> customer.address.post_code
• EMAIL -> customer.email
• PHONE -> customer.phone
• IP -> customer's IP address (collected by Corefy's checkout if not overridden)

Refunds

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

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Partner ID
• Username
• Secret Key
• Member ID
• Terminal ID
• Test Mode -> (enable if you are using sandbox credentials)
• Currency -> multi-select; check with your account manager which are enabled

First request to Corefy API (MIN)

What it does: creates a payout-invoice and sends funds to a card using TransactWorld's own stored card token (not a raw card number).

Payout - MIN

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "0dde9e79-2c64-4703-adaf-93d710633401",
      "service": "card_token",
      "currency": "EUR",
      "amount": 10,
      "fields": {
        "token": "6b1b2e2a-6a7b-4e35-9b1f-1a9a7a9d9c01"
      }
    }
  }
}

Payout - MAX

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "3c6d2f8e-8a2a-4e7a-9b1a-2f6a7b9c0d1e",
      "service": "card_token",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com"
      },
      "fields": {
        "token": "6b1b2e2a-6a7b-4e35-9b1f-1a9a7a9d9c01"
      }
    }
  }
}

This card_token service isn't tied to a single currency - it's available regardless of which currency you select on the connection form.

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.