Re-set

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• API Key
• API Type
• S2S Token (optional)
• Brand ID
• Webhook Public Key (optional)
• API URL (optional)
• Strict Customer Data Validation (optional) -> select which customer fields (phone, name, street, country, individual tax ID, city, post code, region) must be present in your request; if a selected field is missing, Corefy rejects the request upfront instead of forwarding an incomplete one to Re-set.
• Test Mode -> (enable if you are using sandbox credentials)

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

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "9c0d1e23-4f5a-4b6c-8d78-9e0f1a2b3c4d",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "0d1e2f34-5a6b-4c7d-8e89-0f1a2b3c4d5e",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "individual_tax_id": "12345678900",
        "address": {
          "country": "US",
          "region": "NY",
          "city": "New York",
          "full_address": "1 Main street",
          "post_code": "10001"
        }
      }
    }
  }
}

customer is entirely optional unless required by your Strict Customer Data Validation setting. customer.name is forwarded as-is (not split into first/last).

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

• send_true_js_enabled -> optional, boolean - if enabled, always sends javascript_enabled: true to Re-set regardless of the customer's actual browser info; if disabled, sends the real detected value.

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)

• phone -> customer.phone
• full_name -> customer.name
• street_address -> customer.address.full_address
• country -> customer.address.country
• personal_code -> customer.individual_tax_id
• city -> customer.address.city
• zip_code -> customer.address.post_code
• state -> customer.address.region

Refunds

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