PayTech

White label gateway, payment orchestration and financial management technologies. Fully customised to your specifications.

Website: https://pay.tech/

Set up Account Provider account

Step 1: Create Provider account

To create an account send connection request at the https://pay.tech/ or contact manager directly. Submit the required documents to verify your account and gain access.

Step 2: Get required credentials

Credentials that have to be issued:

• API Key — service identifier for PayTech API
• Signing Key — your unique secret key for signing API requests

"Having issues with your credentials?" Please contact our support team!

Connect Provider Account

Step 1. Connect account at the Corefy Dashboard

Press Connect at PayTech Provider Overview page in 'New connection' and choose Provider account option to open Connection form.

Enter credentials:

• API Key — service identifier for PayTech API
• Signing Key — your unique secret key for signing API requests

Also, select Test or Live mode according to the type of account to connect with PayTech.

You have connected PayTech account!

Connect H2H Merchant Account

Step 1. Connect H2H account at the Corefy Dashboard

Press Connect at PayTech Provider Overview page in 'New connection' and choose H2H Merchant account option to open Connection form.

Enter credentials:

• API Key — service identifier for PayTech API
• Signing Key — your unique secret key for signing API requests

Select Test or Live mode according to the type of account to connect with PayTech. Choose Currency: set this parameter according to available currencies for your PayTech account.

You have connected PayTech H2H merchant account!

API examples:

Minimum data set to create a transaction

SALE

POST /api/payment-invoices HTTP/1.1

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 5,
      "customer": {
        "reference_id": "85af8385-d00e-4f58-ab1f-3a527fdf2d3b"
      },
      "test_mode": false,
    }
  }
}

Maximum data set to create a transaction

SALE

POST /api/payment-invoices HTTP/1.1

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "1f2aa3ca-abd8-4741-980d-4017ed30cb8c",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 5,
      "customer": {
        "reference_id": "85af8385-d00e-4f58-ab1f-3a527fdf2d3b",
        "name": "John Doe",
        "email": "johndoe@email.com",
        "phone": "+2134234234523",
        "address": {
          "full_address": "123 Baker street",
          "country": "US",
          "state": "CA",
          "city": "Los Angeles",
          "post_code": "12345"
        }
      },
      "test_mode": false
    }
  }
}

Additional information

Constants

If some parameters are not sent in the transaction creation request, they will take the values from the set constants.

Here is a list of constants with their corresponding parameters:

• FIRST_NAME → customer [first_name]
• LAST_NAME → customer [last_name]
• EMAIL → customer [email]
• PHONE → customer [phone]
• DATE_OF_BIRTH → customer [date_of_birth]
• CITIZENSHIP_COUNTRY_CODE → customer [address] [country]
• FULL_ADDRESS → customer [address] [fullAddress]
• CITY → customer [address] [city]
• COUNTRY_CODE → customer [address] [country]
• POSTAL_CODE → customer[address][post_code]
• STATE → customer [address] [region]
• ROUTING_GROUP → is passed in the request to create transaction in body['customer']['routingGroup'] parameter
• PAYMENT_METHOD → is passed in the request to create transaction in body['paymentMethod'] parameter

These parameters (routingGroup and paymentMethod) are mandatory on PayTech side. Be sure to set values for its constants in the appropriate routes.

Provider Options

• finalize_by_protocol
  • The provider does not guarantee the finality of the fail status because in their system it can later change to success and if the merchant does not agree with this logic then there is no need to enable this option.
    • Then we (Corefy) will stop failing payments but the merchant will not receive transaction status discrepancies.
  • If a merchant wants to fail decline which the provider does not guarantee then you need to enable this option.
• ignore_callback
  • for cascading to work correctly, we exclude the possibility of finalizing payments using asynchronous callbacks, ignore the callback, do not change the status of the transaction on it in any way and rely only on the status request for finalization (Reconciliation)
• save_provider_instant_token
  • if you plan to use the account for instant payments.
• add_additional_data
  • causes the connector to include an additionalParameters field in the payment request sent to PayTech. This field contains the customer's referenceId (as receiverAccountNumber) along with any additional_parameters from the transaction metadata

"Still looking for help connecting your PayTech account?"

Please contact our support team!