Skip to content

Logo

DectaSoap

Supports in this guide: Payments

Provider website: decta.com

Note

This is a SOAP-API connection to DECTA, separate from the already-published Decta connector - they use independent credentials and are not interchangeable.

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

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

Prerequisites: get from DECTA

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

  • Merchant ID -> Corefy field merchant_id.
  • Transaction type -> Corefy field transaction_type -> SMS (single-message, sale in one step) or DMS (dual-message, authorize then capture separately).
  • API URL -> Corefy field api_url.
  • MPI API URL -> Corefy field mpi_api_url -> used for 3D Secure enrollment/validation.
  • Private key -> Corefy field private_key -> uploaded as a file.
  • Merchant certificate -> Corefy field cert -> uploaded as a file.
  • Charge Biller Reference (optional) -> Corefy field charge_biller_ref.
  • Charge Payment Instrument Reference (optional) -> Corefy field charge_payinstr_ref.
  • Reconciliation Biller Reference (optional) -> Corefy field reco_biller_ref.
  • Reconciliation Payment Instrument Reference (optional) -> Corefy field reco_payinstr_ref.
  • Refund Biller Reference (optional) -> Corefy field refund_biller_ref.
  • Refund Payment Instrument Reference (optional) -> Corefy field refund_payinstr_ref.
  • Merchant Gateway ID (optional) -> Corefy field merchant_gateway_id.
  • Final fail transaction (optional) -> Corefy field final_fail_transaction.
  • Use SCA exemptions (optional) -> Corefy field use_sca_exemptions.

Note

The Biller/Payment Instrument Reference fields identify a specific billing configuration on your DECTA account; leave them blank unless DECTA tells you otherwise - each operation (charge, reconciliation, refund) has its own pair.

EUR, USD, GBP.

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

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • Merchant ID
  • Transaction type
  • API URL
  • MPI API URL
  • Private key
  • Merchant certificate
  • Charge / Reconciliation / Refund Biller and Payment Instrument References (optional)
  • Merchant Gateway ID (optional)
  • Final fail transaction (optional)
  • Use SCA exemptions (optional)

Success

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

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "4bfc8d32-8726-4989-a580-2adca8f875cb",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "5c1d9e43-9837-4a90-b691-3bdb9f986dcd",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "customer@example.com",
        "phone": "+15551234567",
        "metadata": {
          "workPhone": "+15559876543",
          "homePhone": "+15551112222"
        }
      }
    }
  }
}

Important

  • customer.email, customer.phone, metadata.workPhone, and metadata.homePhone are only read when the send_contact_field/send_contact_field_required options are enabled (see below).
  • No Constants are configured for regular customer fields - only DWO_MASTERCARD_WALLET_ID exists (see 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

  • qcash_method -> optional, boolean - switches the default billing reference used for SMS/DMS transactions to DECTA's Qcash-specific routing, when a custom Biller/Payment Instrument Reference isn't explicitly set on your account.
  • send_contact_field -> optional, boolean - adds the customer's contact details (email, phone, work phone, home phone) to the 3D Secure enrollment request, when available.
  • send_contact_field_required -> optional, boolean - requires customer.email, customer.phone, metadata.workPhone, and metadata.homePhone to all be present; the payment fails immediately if any of them is missing.

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)

  • DWO_MASTERCARD_WALLET_ID -> Mastercard digital wallet operator ID, used for tokenized Mastercard wallet payments.

Refunds

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

Additional info

  1. Active reconciliation is available - an active status request can finalize the payment.
  2. No recurring - this connector does not support saving/charging a token through Corefy.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify Merchant ID, certificate and private key for the selected environment
  • Payment fails for missing contact details -> send_contact_field_required is enabled; provide customer.email, customer.phone, metadata.workPhone, and metadata.homePhone
  • Currency or service is not supported -> confirm allowed currencies/features in your DECTA account and in Corefy - only EUR, USD, GBP are available
  • Refund fails with multiple attempts -> only one refund per payment is allowed
  • Not sure which Biller/Payment Instrument Reference to use? -> confirm with your DECTA account manager, or leave them blank to use the account's default routing

Question

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