Transact365

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• API Key -> api_key
• Secret Key -> secret_key
• Test Mode -> (enable if you are using sandbox credentials)
• MID ID -> mid_id (optional, leave empty to use the MID ID of the route)
• External ID -> external_id (optional, any unique value of your choice; needed only when you connect several accounts with the same API Key and Secret Key - see "Additional info". It cannot be changed after the connection is created)
• API URL -> api_url (optional, leave empty to use the default endpoint)

Choose Currency and Features. You can set these parameters according to available currencies and features for your Transact365 account, but it is necessary to check details of the connection with your Corefy account manager.

First request to Corefy API (MIN)

What it does: creates a payment-invoice. The customer is redirected to the Transact365 hosted payment page.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "pay_id_aud_hpp",
      "currency": "AUD",
      "amount": 10,
      "customer": {
        "email": "johndoe@email.com"
      }
    }
  }
}

customer [email] is mandatory on the Transact365 side, so send it in every request. The payer IP address and the country are added by Corefy automatically: the country is derived from the currency (AUD -> AU, GBP -> GB, CAD -> CA, MAD -> MA, EGP -> EG), so only these five currencies can be processed.

Other payment services use exactly the same request shape, only the service and currency values change: openbanking_gbp_hpp (Open Banking, GBP), interac_cad_hpp (Interac, CAD), mobile_money_mad_hpp / mobile_money_egp_hpp (Mobile money, MAD / EGP) and bank_transfer_mad_hpp / bank_transfer_egp_hpp (Bank transfer, MAD / EGP).

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "1f2aa3ca-abd8-4741-980d-4017ed30cb8c",
      "service": "pay_id_aud_hpp",
      "currency": "AUD",
      "amount": 10.04,
      "customer": {
        "reference_id": "85af8385-d00e-4f58-ab1f-3a527fdf2d3b",
        "name": "John Doe",
        "email": "johndoe@email.com",
        "phone": "+610000000000",
        "metadata": {
          "ip": "203.0.113.10"
        }
      },
      "test_mode": false
    }
  }
}

Apart from customer [email], all customer data is optional and is sent to Transact365 only when present: customer [name] is split into the first and the last name of the payer, customer [phone] is sent as the payer mobile number, and customer [metadata] [ip] overrides the payer IP address that Corefy detects itself.

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

Connect Provider account in Corefy Dashboard

Payouts use the same Provider account as payments. If you already connected one, no separate connection is required.

Step 1 - Open connection form

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

Step 2 - Fill in fields (provider -> Corefy)

• API Key -> api_key
• Secret Key -> secret_key
• Test Mode -> (enable if you are using sandbox credentials)
• MID ID -> mid_id (optional, leave empty to use the MID ID of the route)
• External ID -> external_id (optional, any unique value of your choice; needed only when you connect several accounts with the same API Key and Secret Key - see "Additional info". It cannot be changed after the connection is created)
• API URL -> api_url (optional, leave empty to use the default endpoint)

First request to Corefy API (MIN)

What it does: creates a payout-invoice.

Payout - MIN

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "service": "bank_transfer_egp",
      "currency": "EGP",
      "amount": 10,
      "customer": {
        "email": "johndoe@email.com"
      },
      "fields": {
        "account_number": "0123456789012345",
        "beneficiary_name": "John",
        "beneficiary_lastname": "Doe"
      }
    }
  }
}

customer [email] and the payer IP address are mandatory on the Transact365 side. The IP address is taken from customer [metadata] [ip] of the request, or from the IP constant of the route (see "Constants") - set at least one of them, otherwise Transact365 rejects the payout.

The payout destination goes to fields (or to customer, depending on the method). Each payout service expects its own set of values:

If none of the values of the chosen method is present in the request, Corefy does not call Transact365 at all and fails the payout with Missing payout requisites. Values that are missing but not mandatory for the beneficiary are requested by Transact365 from the customer in a web form.

Payout - MAX

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "3b1c9d52-0f41-47a0-9a1e-6c2f8b5d7e10",
      "service": "bank_transfer_egp",
      "currency": "EGP",
      "amount": 10,
      "description": "Payout for order 123456",
      "customer": {
        "reference_id": "85af8385-d00e-4f58-ab1f-3a527fdf2d3b",
        "name": "John Doe",
        "email": "johndoe@email.com",
        "metadata": {
          "ip": "203.0.113.10"
        }
      },
      "fields": {
        "account_number": "0123456789012345",
        "beneficiary_name": "John",
        "beneficiary_lastname": "Doe",
        "beneficiary_phone": "+201000000000",
        "beneficiary_document_id": "29001011234567",
        "bank_code": "CIB"
      },
      "test_mode": false
    }
  }
}

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.

If a field is missing in the API request, Corefy can take the value from the configured Constants.

After the successful connection, fill in constants for necessary routes in editing menu.

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)

• IP -> customer.metadata.ip