Paysecure

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• API Key
• API Type -> Server to Server
• S2S Token (optional)
• Brand ID
• Webhook Public Key (optional)
• Strict Customer Data Validation -> multi-select the customer fields you want Corefy to hard-require on every transaction (see note below)
• Test Mode -> (enable if you are using sandbox credentials)

Choose Currency and Features. USD and EUR are confirmed; 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.

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,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com"
      }
    }
  }
}

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",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "individual_tax_id": "123456789",
        "address": {
          "full_address": "1 Main street",
          "country": "US",
          "region": "California",
          "city": "Los Angeles",
          "post_code": "90001"
        }
      }
    }
  }
}

customer.address.region is matched against Paysecure's own state/subdivision list using a fuzzy lookup (it accepts a full state name or an ISO code, in any case) and converted to the code Paysecure expects - if it can't be resolved, the country code is sent in its place instead. This connector also supports Apple Pay and Google Pay on this same account (no separate service code needed).

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

Options are configured on the Corefy side and affect how Corefy builds provider requests or processes responses.

Currently available options (4)

• check_trans_allowed - asks Paysecure to pre-verify the customer is allowed to transact before creating the purchase.
• finalize_on_complete_sale - actively determines the final status right after the 3D Secure challenge completes, instead of relying only on that response.
• ftd_transaction - flags whether this is a first-time-deposit transaction.
• ignore_callback - tells Corefy to disregard Paysecure's own callback notifications entirely.

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)

• FULL_NAME -> customer.name
• PHONE -> customer.phone
• STREET_ADDRESS -> customer.address.full_address
• COUNTRY -> customer.address.country
• PERSONAL_CODE -> customer.individual_tax_id
• CITY -> customer.address.city
• ZIP_CODE -> customer.address.post_code
• STATE -> customer.address.region

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Brand ID
• API Key
• Webhook Public Key (optional)
• Currency -> single-select

First request to Corefy API (MIN)

What it does: creates a payment-invoice and returns a redirect link to the chosen local method's payment page.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8e3dbbb0-17af-4c9a-bedb-93bdac6900a2",
      "service": "pix_brl_hpp",
      "currency": "BRL",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "pix_brl_hpp",
      "currency": "BRL",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "phone": "+5511999999999"
      },
      "fields": {
        "cpf_number": "70634982826"
      }
    }
  }
}

fields.cpf_number (the customer's Brazilian tax ID) is required for PIX specifically. This connector also supports QuickBit in EUR/NOK/SEK (use quick_bit_<ccy>_hpp), bank transfer in JPY/AUD (use bank_transfer_<ccy>_hpp), and Interac e-Transfer in CAD (use interac_cad_hpp - customer.address.country is forwarded as CA automatically for this one).

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.

Connect Provider account in Corefy Dashboard

Uses the same Provider account connection as Payments above - one connection covers both directions, there's nothing extra to fill in for payouts specifically.

First request to Corefy API (MIN)

What it does: creates a payout-invoice and sends funds via PIX or Interac e-Transfer.

Payout - MIN (PIX, Brazil)

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "0dde9e79-2c64-4703-adaf-93d710633401",
      "service": "pix_brl",
      "currency": "BRL",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com"
      },
      "fields": {
        "cpf_number": "70634982826",
        "document_type": "CPF"
      }
    }
  }
}

Payout - MIN (Interac, Canada)

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "3c6d2f8e-8a2a-4e7a-9b1a-2f6a7b9c0d1e",
      "service": "interac_cad",
      "currency": "CAD",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com",
        "address": {
          "country": "CA"
        }
      },
      "fields": {
        "cpf_number": "70634982826",
        "document_type": "CPF"
      }
    }
  }
}

The recipient's name can come from customer.name, or from fields.beneficiary_name/fields.beneficiary_lastname if you'd rather not put it in customer.

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.