Vendo

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Merchant ID
• Site ID
• Secret Key
• Gateway API Secret Key
• 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 Vendo account; confirm with your account manager.

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. Vendo may return a 3D Secure challenge redirect depending on the card.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8f0a2c41-3b5d-4e6f-8a0c-7b9d1e3f5a7c",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "9a1b3c52-4c6e-4f70-9b1d-8c0e2f4a6c8e",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "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. For first/last name, the priority is customer.name first, then the name embossed on the card, then 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

No Options are configured for this connector.

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
• first_name -> customer.name (first part)
• last_name -> customer.name (second part)
• country_code -> customer.address.country
• city -> customer.address.city
• address -> customer.address.full_address
• post_code -> customer.address.post_code
• language -> no matching request field; defaults to English if not set

Recurring (save and charge a token)

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

Vendo supports partial refunds, but only one refund per payment (no multiple partial refunds against the same payment). Refund status updates rely entirely on Vendo's callback - active status checks (reconciliation) for a refund aren't available.

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Merchant ID
• Site ID
• Secret Key
• Gateway API 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 Vendo-hosted page to complete a bank transfer or SEPA transfer payment.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "0b2c4d63-5d7f-4a81-8c2e-9d1f3a5c7e9f",
      "service": "bank_transfer_eur_hpp",
      "currency": "EUR",
      "amount": 10
    }
  }
}

This flow also supports USD, CAD for bank transfer, and sepa_transfer_eur_hpp/sepa_transfer_usd_hpp/sepa_transfer_cad_hpp for SEPA transfer.

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "1c3d5e74-6e80-4b92-8d3f-0e2a4c6e8f0a",
      "service": "bank_transfer_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "address": {
          "country": "FR",
          "region": "IDF",
          "city": "Paris",
          "full_address": "1 Main street",
          "post_code": "75000"
        }
      }
    }
  }
}

customer is entirely 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 Options are configured for this flow.

Constants (fallback fields)

Same priority rule as the H2H Merchant account above.

Currently available constants (constant -> Corefy API field)

• email -> customer.email
• phone -> customer.phone
• first_name -> customer.name (first part)
• last_name -> customer.name (second part)
• country -> customer.address.country
• region -> customer.address.region
• city -> customer.address.city
• full_address -> customer.address.full_address
• post_code -> customer.address.post_code
• language -> no matching request field
• ip -> customer.metadata.ip
• iban -> only used for SEPA transfer - this is your own receiving IBAN, normally taken automatically from your Corefy merchant profile; this constant is only a fallback for when that's not set.

Refunds

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