Skip to content

Logo

Siquro New

Unique Payment Gateway

Supports in this guide: Payments

Provider website: siquro.com

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

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

Prerequisites: get from Siquro

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

  • Merchant ID -> Corefy field merchant_id.
  • API Key -> Corefy field api_key.
  • Signature Key -> Corefy field signature_key -> used to verify callback notifications from Siquro.
  • API URL (optional) -> Corefy field api_url -> leave as default unless your account manager tells you otherwise.

Note

This is a separate connection from the Siquro connector already available in Corefy - that one is a different, older integration. Confirm with your account manager which one applies to your account.

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

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • Merchant ID
  • API Key
  • Signature Key
  • API URL (optional)
  • Test Mode -> (enable if you are using sandbox credentials)

Choose Currency / Features; check with your Corefy account manager which are enabled for your account.

Success

You have connected Siquro New 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. Siquro may return an authentication redirect depending on the card.

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
    }
  }
}

This connector also supports USD.

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",
        "address": {
          "country": "FR"
        }
      }
    }
  }
}

customer is entirely optional - everything is only used to enrich the sale.

Important

customer.name is only forwarded to Siquro when both first and last name are available - if only one is present, neither is 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

Options

  • finalize_by_protocol_in_minutes -> optional, number (minutes, 5 or more) - if Siquro reports a payment as failed or cancelled, Corefy still keeps it as pending (requiring reconciliation) until this many minutes have passed since the payment was created, in case a delayed or out-of-order status update still arrives from Siquro's own protocol; after that, the failed/cancelled result is treated as final.

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)

  • email -> customer.email
  • country -> customer.address.country (2-letter country code)
  • brand -> your Corefy merchant profile's website URL, if one is set

Note

brand isn't related to the card's brand (Visa/Mastercard/etc.) - it identifies your business to Siquro and normally comes from your Corefy merchant profile automatically; the constant is only a fallback for when that's not set.

Additional info

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

FAQ / Troubleshooting

  • A failed/cancelled payment stays pending longer than expected -> this is expected behavior when finalize_by_protocol_in_minutes is set - Corefy waits out the grace period before finalizing
  • Invalid credentials / auth error -> verify Merchant ID/API Key for the selected environment
  • Currency or service is not supported -> confirm allowed currencies/features in your Siquro account and in Corefy
  • Not sure if this is the right Siquro connector? -> this one (Siquro New) is a separate, newer integration from the existing Siquro connector in Corefy - confirm with your account manager

Question

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