Walletto

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Login
• Password
• SSL Certificate
• SSL Password
• API URL (optional)
• Save OCT Token -> enable if you plan to use token-based payouts (see Payouts below) or stored-credential recurring charges
• 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. Walletto may return a 3D Secure (v1 or v2) challenge 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
    }
  }
}

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",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "address": {
          "country": "FR"
        }
      }
    }
  }
}

customer is entirely optional - email/phone/address.country are only used to enrich fraud-screening data sent to Walletto, never to block 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

Options

Configured per service (payment_card_<ccy>_hpp):

• time_to_finalize -> optional, number (minutes) - how long Corefy waits for a final status before failing a still-pending payment with a timeout.
• always_force3d -> optional, boolean - forces a 3D Secure challenge on every sale, regardless of what Walletto would otherwise decide.
• amount_indicator / frequency_indicator -> optional, Fixed/Variable - see Recurring / stored-credential setup below; only relevant if you use recurring charges.

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)

• OS -> device operating system sent for fraud screening
• OS_VERSION -> device OS version sent for fraud screening
• PLUGINS -> browser plugins sent for fraud screening
• IS_MOBILE -> whether the checkout device is mobile

These four apply to both regular card payments and Apple Pay/Google Pay sales (see Additional info below). Two more constants exist specifically for recurring / stored-credential setup - see the next section.

Recurring / stored-credential setup

If you charge a saved card later without the customer present (subscriptions, installments), Walletto requires explicit stored-credential indicators on both the initial sale and every subsequent charge:

• INITIAL_RECURRING_INDICATOR (constant, used on the first sale) -> one of Credential on file, Initiate, Fixed amount and frequency, Installment.
• RECURRING_INDICATOR (constant, used on subsequent recurring charges) -> one of Credential on file, Unscheduled, Fixed frequency, Fixed amount and frequency, Installment.
• FREQUENCY / DAYS_TO_END (constants) -> required only when the frequency_indicator Option is set to Fixed - the number of days between charges and the total number of days the series runs.

Refunds

Walletto supports partial and multiple refunds against the same payment.

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Login
• Password
• SSL Certificate
• SSL Password
• API URL (optional)
• Test Mode -> (enable if you are using sandbox credentials)

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

Payout - MAX

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "3c6d2f8e-8a2a-4e7a-9b1a-2f6a7b9c0d1e",
      "service": "payment_card_eur",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "metadata": {
          "date_of_birth": "1990-01-01"
        }
      },
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

customer is entirely optional - name/date of birth, when sent, are only forwarded to Walletto as recipient details.

Payout - token-based (requires Save OCT Token enabled)

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "a1b2c3d4-e5f6-4789-a0b1-c2d3e4f5a6b7",
      "service": "card_token",
      "currency": "EUR",
      "amount": 10,
      "fields": {
        "token": "6b1b2e2a-6a7b-4e35-9b1f-1a9a7a9d9c01"
      }
    }
  }
}

card_token pays out to a card already tokenized through a Walletto sale on your H2H Merchant account (with Save OCT Token enabled) - it isn't tied to a specific currency.

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.