SLYSE

Smart payments that convert, scale globally, and drive real growth

Supports in this guide: Payments

Provider website: slyse.me

What you need to do for start processing transactions (brief summary)

Choose account type
Get your credentials (from SLYSE)
Connect in Dashboard
Send an API request

Choose account type

SLYSE can be connected in different ways (depending on your needs):

If you do H2H card payments (card data sent directly, or posted straight from the customer's browser) -> choose H2H Merchant account
If you do Apple Pay or Google Pay payments via a hosted page -> choose Provider account

SLYSE does not currently support payouts through Corefy. If you're not sure which one to use, confirm with your Corefy account manager.

Prerequisites: get from SLYSE

Contact your SLYSE account manager to get your account verified and receive the following credentials. H2H Merchant account and Provider account are separate connections with independent credentials, even though the field names are similar.

For H2H Merchant account:

API Key -> Corefy field api_key.
API Type -> Corefy field api_type -> server_to_server or direct_post (see the important note below).
S2S Token (required only for server_to_server) -> Corefy field s2s_token.
Brand ID -> Corefy field brand_id.
Webhook Public Key (optional) -> Corefy field webhook_public_key -> used to verify callback notifications from SLYSE, if your account requires it.
API URL (optional) -> Corefy field api_url -> leave as default unless your account manager tells you otherwise.

For Provider account:

Login -> Corefy field login.
Brand ID -> Corefy field brand_id.
API Key -> Corefy field api_key.
Webhook Public Key (optional) -> Corefy field webhook_public_key.
Currency -> Corefy field currency -> EUR.

Important

API Type decides how card data is submitted: with direct_post, the customer's browser posts card details straight to SLYSE's own hosted form (card data never passes through Corefy); with server_to_server, Corefy submits the card data on the customer's behalf, which requires S2S Token.

Payments processing (connect H2H Merchant account, create payment-invoice)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

API Key
API Type
S2S Token (required only for server_to_server)
Brand ID
Webhook Public Key (optional)
API URL (optional)
Test Mode -> (enable if you are using sandbox credentials)

Corefy doesn't restrict currencies for this connector in advance - available currencies depend entirely on what's enabled for your SLYSE account; confirm with your account manager.

Success

You have connected SLYSE H2H Merchant 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. SLYSE may return a 3D Secure challenge redirect depending on the card.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "4f6a1b2c-3d4e-4f5a-9b6c-7d8e9f0a1b2c",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "email": "johnsmith@gmail.com"
      }
    }
  }
}

Important

customer.email is required - the sale is rejected outright ("Customer email is required") if it's missing, even though customer is normally optional on Corefy's API.

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8a9b0c1d-2e3f-4a5b-6c7d-8e9f0a1b2c3d",
      "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": "12345678900",
        "address": {
          "country": "FR",
          "region": "IDF",
          "city": "Paris",
          "full_address": "1 Main street",
          "post_code": "75000"
        }
      }
    }
  }
}

customer.individual_tax_id is forwarded to SLYSE as the payer's personal/tax code, if provided.

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 connector.

Refunds

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

Payments processing (connect Provider account, create payment-invoice)

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

Login
Brand ID
API Key
Webhook Public Key (optional)
Currency -> EUR
Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected SLYSE Provider account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice and redirects the customer to a SLYSE-hosted page to complete the payment with Apple Pay or Google Pay. This flow is EUR only and doesn't support generic card payments - use the H2H Merchant account for cards.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "1c2d3e4f-5a6b-4c7d-8e9f-0a1b2c3d4e5f",
      "service": "applepay_eur_hpp",
      "currency": "EUR",
      "amount": 10
    }
  }
}

This flow also supports googlepay_eur_hpp.

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6b7c8d9e-0f1a-4b2c-9d3e-4f5a6b7c8d9e",
      "service": "applepay_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com"
      }
    }
  }
}

customer is optional - everything is only used to prefill the hosted form, it never blocks the sale.

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 Constants are configured for this flow.

Options

finalize_by_protocol -> optional, boolean - changes how Corefy interprets certain status codes returned by SLYSE; leave disabled unless your account manager tells you otherwise.

Refunds

This flow does not support refunds - use the H2H Merchant account if you need refunds.

Additional info

Callback routing is automatic - Corefy generates the callback/return URLs per transaction, nothing to configure in SLYSE's own back-office.
No payouts - this connector does not support payouts through Corefy.

FAQ / Troubleshooting

Sale fails with "Customer email is required" -> this only applies to the H2H Merchant account - send customer.email with every sale
Invalid credentials / auth error -> verify the credentials for the selected account type and environment - H2H Merchant account and Provider account use entirely different credential sets
Card data not accepted / form shown twice -> check whether API Type is set to direct_post or server_to_server as expected for your account
Refund fails on the Provider account flow -> refunds aren't supported there - use the H2H Merchant account instead
Currency or service is not supported -> confirm allowed currencies/features in your SLYSE account and in Corefy - the Provider account is EUR only

Question

Still looking for help connecting your SLYSE account? Please contact our support team!