Securepaycard

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Public Key
• Secret Key
• API Type
• Terminal ID
• Save Instant Token (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.

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 - non-CVV sales aren't supported. There's no merchant-side control over 3D Secure - it's handled transparently based on the card/issuer.

Payment - MIN

POST /api/payment-invoices

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

This connector also supports EUR.

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "address": {
          "country": "US",
          "region": "NY",
          "city": "New York",
          "full_address": "1 Main street",
          "post_code": "10001"
        }
      }
    }
  }
}

customer is entirely optional - anything you don't send falls back to the Constants below.

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

• use_default_browser_info -> optional, boolean - if Corefy couldn't collect the customer's real browser fingerprint, sends a generic placeholder browser profile instead of omitting it.
• send_client_ip -> optional, boolean - forwards the customer's real IP address to Securepaycard, instead of omitting it.
• ignore_callback -> optional, boolean - for cascading to work correctly, excludes finalizing the payment from the asynchronous callback; Corefy then relies only on an active status request (reconciliation) to finalize it.

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
• PHONE -> customer.phone
• ADDRESS -> customer.address.full_address
• CITY -> customer.address.city (also falls back to a city derived from the customer's IP address before this constant is used)
• STATE -> customer.address.region
• POSTCODE -> customer.address.post_code
• COUNTRY -> customer.address.country

Recurring (save and charge a token)

If Save Instant Token is enabled on your connection, this connector supports saving the card as a token during a sale (via Corefy's standard tokenize-on-sale request) and later charging that same token without sending full card data again.

Refunds

Securepaycard supports full refunds only (no partial refunds), and only one refund per payment.

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Public Key
• Secret Key
• Test Mode -> (enable if you are using sandbox credentials)

First request to Corefy API (MIN)

What it does: creates a payment-invoice and redirects the customer to a Securepaycard-hosted page to complete the payment.

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 flow also supports UAH, AUD, CAD.

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 isn't forwarded on this flow at all - this connection doesn't pass any customer details to Securepaycard.

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.

Refunds

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

Connect Provider account in Corefy Dashboard

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

First request to Corefy API (MIN)

What it does: creates a payout-invoice and sends funds directly to a card.

Payout - MIN

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "0dde9e79-2c64-4703-adaf-93d710633401",
      "service": "payment_card_eur",
      "currency": "EUR",
      "amount": 10,
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

This flow also supports UAH, USD.

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.