Skip to content

Logo

Siquro

Unique Payment Gateway. Accept payments with us and open up new markets and opportunities in the online payments industry.

Supports in this guide: Payments, Payouts

Provider website: siquro.com

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

  1. Choose account type
  2. Get your credentials (from Siquro)
  3. Connect in Dashboard
  4. Send an API request

Choose account type

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

  • If you do direct card payments (with refunds) -> choose H2H Merchant account
  • If you do open banking / bank-redirect payments, or payouts -> choose Provider account

These are two separate, independent connections with their own credentials. If you're not sure which one to use, confirm with your Corefy account manager.

Prerequisites: get from Siquro

Contact your Siquro account manager to get your account verified and receive the following credentials.

For H2H Merchant account:

  • API key -> Corefy field api_key.
  • API type -> Corefy field api_type -> server to server or direct post; confirm with your Siquro manager which one applies to your account.
  • S2S token (optional) -> Corefy field s2s_token -> only needed when API type is server to server.
  • Brand ID -> Corefy field brand_id.
  • Webhook public key (optional) -> Corefy field webhook_public_key -> uploaded as a file; used to verify webhook/callback signatures.

For Provider account:

  • Merchant ID -> Corefy field merchant_id -> example: 12345 -> where to find: Siquro backoffice / issued by Siquro manager
  • Header key -> Corefy field header_key -> example: hk_9f2c4e7a1b -> used together with Merchant ID to authorize API requests -> where to find: Siquro backoffice / issued by Siquro manager
  • Signature key -> Corefy field signature_key -> example: sk_3d8a6b0c5e -> used to verify the signature of callbacks sent by Siquro -> where to find: Siquro backoffice / issued by Siquro manager

USD, EUR (H2H Merchant account); EUR (Provider account Payments, open banking / bank-redirect); SEPA transfer (Provider account Payouts).

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

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

Open Siquro in the provider directory and press Connect at Siquro 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 (optional)
  • Brand ID
  • Webhook public key (optional)

Success

You have connected Siquro 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. CVV is always required. Siquro may return a 3D Secure challenge redirect depending on the card.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6be05631-8710-4b14-a369-1928a2b70eda",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6efdb1fa-c69f-43de-b7b8-ca5c73d0ff28",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "test@example.com"
      }
    }
  }
}

Important

No Constants or Options are configured for this flow - if a customer field is missing, it's simply not sent.

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

Refunds

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

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

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • Merchant ID -> merchant_id
  • Header key -> header_key (used to authorize API requests)
  • Signature key -> signature_key (used to verify callback signatures)

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

Success

You have connected Siquro Provider account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice.

Siquro requires the customer's email, first and last name, and country for every payment. Send them in the request (as below), or set them once as Constants on the connection (see "Constants" below). When the constants are set, you can leave out the customer fields they cover.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8afec793-9b41-4dc4-b281-c76cc54ffb89",
      "service": "bbva_eur_hpp",
      "currency": "EUR",
      "amount": 100,
      "test_mode": false,
      "customer": {
        "reference_id": "33cc9165-6ab2-4cee-8d9a-10f05cddbb5a",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "address": {
          "country": "ES"
        }
      }
    }
  }
}

Payment - MAX

POST /api/payment-invoices

In addition to MIN:

  • customer.metadata.website_url -> sent to Siquro as the merchant's brand/website
  • service_fields.iban_number -> the payer's IBAN, sent to Siquro when your service collects it
{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "06fa1ea9-8a5b-4dbc-b67b-6236b3b9af3d",
      "service": "bbva_eur_hpp",
      "currency": "EUR",
      "amount": 100,
      "test_mode": false,
      "customer": {
        "reference_id": "58acf793-9b41-4dc4-b281-c76cc54ff230",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "address": {
          "country": "ES"
        },
        "metadata": {
          "website_url": "https://example.com"
        }
      },
      "service_fields": {
        "iban_number": "DE89370400440532013000"
      }
    }
  }
}

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 (1):

  • dedicated_banking - redirects the customer straight to the selected bank instead of the generic payment method page.
dedicated_banking

What it does: when enabled, Corefy creates the payment through Siquro's dedicated bank flow. The customer is redirected directly to the bank that matches the selected service, skipping the bank selection step. When disabled, the payment is created through Siquro's generic payment method flow.

When to use: enable it for bank-specific open banking services (for example santander_eur_hpp, bbva_eur_hpp, lacaixa_eur_hpp, bancsabadell_eur_hpp, banco_bpi_eur_hpp, bper_banca_eur_hpp, banco_bpm_eur_hpp, ing_eur_hpp, revolut_bank_eur_hpp, n26_bank_eur_hpp, wise_eur_hpp) when you want the customer to land directly on their bank's page.

Default: "false"

Allowed values: true / false

Note

If you are not sure which value to select, please contact our support team!

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.

So, 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 and value isn't present in the request -> 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)

  • email -> customer.email
  • first_name -> customer.name (first name part)
  • last_name -> customer.name (last name part)
  • country -> customer.address.country

Refunds

This flow does not support refunds through Corefy's API. A provider-initiated refund can still be reflected on the payment via callback if Siquro reports one on their side.

Payouts processing (connect Provider account, create payout-invoice)

Connect Provider account in Corefy Dashboard

Uses the same Provider account connected above - no separate connection step.

First request to Corefy API (MIN)

What it does: creates a payout-invoice and sends a SEPA bank transfer.

Payout - MIN

POST /api/payout-invoices 

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "b4e6f5a7-8d9c-4b0f-9e3e-4d5c6b7f8a9b",
      "service": "sepa_transfer_eur",
      "currency": "EUR",
      "amount": 100,
      "fields": {
        "account_number": "DE89370400440532013000",
        "beneficiary_first_name": "John",
        "beneficiary_last_name": "Doe",
        "beneficiary_country": "DE"
      }
    }
  }
}

Payout - MAX

POST /api/payout-invoices 

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "c5f7a6b8-9e0d-4c1f-9f4f-5e6d7c8a9b0c",
      "service": "sepa_transfer_eur",
      "currency": "EUR",
      "amount": 100,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Doe",
        "address": {
          "country": "DE",
          "city": "Berlin",
          "full_address": "Main street 1"
        },
        "individual_tax_id": "12345678901"
      },
      "fields": {
        "account_number": "DE89370400440532013000",
        "beneficiary_bank_swift_code": "COBADEFFXXX",
        "beneficiary_bank_name": "Commerzbank",
        "bank_country": "DE"
      }
    }
  }
}

Important

  • Beneficiary name/address/tax ID can be sent either directly as fields.beneficiary_* or taken from the matching customer field (customer.name, customer.address, customer.individual_tax_id) - whichever is present; fields values take priority.
  • The payment purpose/comment is taken from fields.payment_purpose, falling back to the payout's description, then the provider reference ID.

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

Refunds

Siquro does not support refunds for payouts.

Additional info

  1. Two independent connections - H2H Merchant account and Provider account use entirely separate credentials and serve different flows; connecting one does not affect the other.
  2. Active reconciliation - available on the H2H Merchant account and on both Payments and Payouts of the Provider account, in addition to callbacks.
  3. No recurring - neither connection supports saving/charging a token through Corefy.
  4. A separate, newer "Siquro New" connector exists on Corefy with its own documentation and its own Dashboard connection - it is not the same account as this one.
  5. Callback routing is handled automatically - you don't need to set up a callback URL in the Siquro backoffice.
  6. For santander_eur_hpp with dedicated_banking enabled (Provider account), the Santander bank is selected by customer.address.country:
    • PT -> Banco Santander Totta (Portugal)
    • GB -> Santander UK
    • any other country -> Banco Santander (Spain)

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify the credentials for the selected account type - H2H Merchant account and Provider account use entirely different credential sets
  • Refund fails with multiple attempts -> only one refund per payment is allowed, and only on the H2H Merchant account
  • Currency or service is not supported -> confirm allowed currencies/features in your Siquro account and in Corefy - each account type supports a different currency/service set
  • Missing customer data fields (Provider account Payments) -> set constants (see "Constants") or provide customer.email, customer.name and customer.address.country in the API request
  • Customer is not redirected directly to the bank -> check that dedicated_banking is enabled for the bank service you use
  • Not sure which account type to use? -> H2H Merchant account is for direct card Payments with refunds; Provider account is for open banking / bank-redirect Payments and SEPA Payouts

Question

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