VisaNet Connect

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

Core credentials

• User ID -> user_id
• Password -> password
• Client ID -> client_id -> required unless you use the Card-to-Account (C2A) mode below
• Acceptor ID -> acceptor_id
• Terminal ID -> terminal_id
• SSL Certificate -> ssl_cert (upload file)
• SSL Private Key -> ssl_private_key (upload file)
• MLE Key ID -> mle_key_id
• MLE Server Certificate -> mle_server_cert (upload file)
• MLE Private Key -> mle_private_key (upload file)
• Test Mode -> test_mode -> (enable if you are using sandbox credentials)

3DS Provider (3ds_provider, optional, default Cybersource) selects which backend handles the mandatory 3-D Secure v2 authentication step for card payments:

• If set to Cybersource, also provide: Cybersource Org ID -> cb_org_id, Cybersource Key -> cb_key, Cybersource Shared Secret -> cb_shared_secret
• If set to Upc, also provide: UPC Merchant ID -> upc_merchant_id, UPC Terminal ID -> upc_terminal_id, UPC Private Key -> upc_private_key (upload file)

Save Instant Token -> save_instant_token -> (enable if you plan to use instant/recurring payments; stores a Visa network token). When enabled, also provide: Tokenization MLE Key ID -> tokenize_mle_key_id, Tokenization MLE Private Key -> tokenize_mle_private_key (upload file), Tokenization Org ID -> tokenize_org_id

API type -> api_type -> optional, default Card Payment. Advanced: switches the connection to Visa Direct Card-to-Account (C2A) mode instead of the standard 3-D Secure card payment flow described above. When set to Card-to-Account, also provide Acquiring BIN -> acquiring_bin and Acquirer Country Code -> acquirer_country_code, and leave 3DS Provider unset or set to Cybersource (Upc is not supported in this mode).

API URL -> api_url -> optional, overrides the default VisaNet API endpoint; leave blank unless instructed otherwise by your Visa relationship manager.

Additionally, choose Currency and Features. You can set these parameters according to available currencies and features for your VisaNet Connect account, but it is necessary to check details of the connection with your Corefy account manager.

First request to Corefy API (MIN)

What it does: creates a payment-invoice.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "c7513313-648f-422d-b17d-8884606f22c3",
      "service": "payment_card_uah_hpp",
      "currency": "UAH",
      "amount": 50
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "35584634-020c-475f-b6ed-09aa656f3564",
      "service": "payment_card_uah_hpp",
      "currency": "UAH",
      "amount": 100,
      "customer": {
        "reference_id": "b84dbf31-6764-49d6-a06c-9848bcbc83a5",
        "name": "John Doe",
        "email": "johndoe@email.com",
        "phone": "+380665544332",
        "address": {
          "country": "US",
          "region": "CA",
          "city": "LA",
          "street": "Some street",
          "post_code": "94111"
        }
      }
    }
  }
}

The customer/address fields above are optional at the API level, but recommended: VisaNet Connect's 3-D Secure step (Cybersource or UPC) and address-verification checks use them for risk scoring. If a field is missing from the request, VisaNet Connect falls back to the matching Constant (see below) or sends it empty.

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

Options are configured on the Corefy side and affect how Corefy builds provider requests or processes responses.

Currently available options (8)

• use_original_id_in_void - sends the original provider transaction ID (instead of Corefy's own) in the void request.
• customer_name_format - defines the order VisaNet Connect uses when splitting a single customer.name into first/last/middle parts.
• enable_reconciliation_for_three_ds - controls whether a Reconcile request can finalize a transaction that is still pending 3-D Secure verification (Card-to-Account mode).
• finalize_by_protocol_in_minutes - if the 3-D Secure challenge never completes within this many minutes, a Reconcile request finalizes the transaction as failed instead of waiting indefinitely.
• skip_auto_browser_info_collect_for_upc - skips VisaNet Connect's automatic browser-data collection request to UPC.
• send_recipient_and_sender_data - adds Sender/Recipient identification and address blocks to the request (Card-to-Account mode only).
• verify_with_zero_amount - sends a zero authorization amount to Cybersource for the Verify operation instead of the requested amount.
• enable_ani_verification - runs a Cybersource Account Name Inquiry (ANI) check during Verify, confirming the cardholder name against the account on file.

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)

Customer/address fallbacks (used on every card payment):

• FIRST_NAME -> customer.name (first part)
• LAST_NAME -> customer.name (last part)
• MIDDLE_NAME -> customer.name (middle part)
• PHONE -> customer.phone
• EMAIL -> customer.email
• ADDRESS -> customer.address.full_address
• CITY -> customer.address.city
• COUNTRY -> customer.address.country
• POST_CODE -> customer.address.post_code

Merchant profile fallbacks (sent as part of every card payment request; used instead of your Corefy Merchant Profile settings):

• PROFILE_WEBSITE_URL -> your business website/contact info
• PROFILE_COMPANY_NAME -> your business (short) name
• PROFILE_COUNTRY_CODE -> your business country
• PROFILE_POST_CODE -> your business postal code
• PROFILE_MCC -> your Merchant Category Code

Card-to-Account (C2A) mode only:

• BUSINESS_APPLICATION_ID -> Visa Direct business application ID
• SOURCE_OF_FUNDS_CODE -> source-of-funds code
• CARD_ACCEPTOR_NAME -> card acceptor (merchant) name
• CARD_ACCEPTOR_ADDRESS_COUNTRY -> card acceptor address country
• CARD_ACCEPTOR_ADDRESS_STATE -> card acceptor address state
• CARD_ACCEPTOR_ADDRESS_CITY -> card acceptor address city
• POS_CONDITION_CODE -> point-of-service condition code
• PAN_ENTRY_MODE -> PAN entry mode code
• PURPOSE_OF_PAYMENT -> purpose-of-payment code
• MOTO_ECI_INDICATOR -> MOTO/e-commerce indicator
• PAYMENT_FACILITATOR_ID -> payment facilitator ID
• PAYMENT_FACILITATOR_NAME -> payment facilitator name
• PAYMENT_FACILITATOR_SUB_MERCHANT_ID -> payment facilitator sub-merchant ID

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields (provider -> Corefy)

• User ID -> user_id
• Password -> password
• Terminal ID -> terminal_id
• Acceptor ID -> acceptor_id
• Acquiring BIN -> acquiring_bin -> your Visa Direct acquiring Bank Identification Number
• Acquirer Country Code -> acquirer_country_code
• SSL Certificate -> ssl_cert (upload file)
• SSL Private Key -> ssl_private_key (upload file)
• MLE Key ID -> mle_key_id
• MLE Private Key -> mle_private_key (upload file)
• MLE Server Certificate -> mle_server_cert (upload file)
• API URL -> api_url -> optional, overrides the default VisaNet API endpoint
• Test Mode -> test_mode -> (enable if you are using sandbox credentials)

First request to Corefy API (MIN)

What it does: creates a payout-invoice.

Payout - MIN

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "eae08d28-1a7a-407f-ab4d-2c8275ca7964",
      "service": "payment_card_uah",
      "currency": "UAH",
      "amount": 10,
      "fields": {
        "card_number": "411111******1111"
      }
    }
  }
}

Payout - MAX

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "58acf793-9b41-4dc4-b281-c76cc54ff230",
      "service": "payment_card_uah",
      "currency": "UAH",
      "amount": 10,
      "customer": {
        "reference_id": "33cc9165-6ab2-4cee-8d9a-10f05cddbb5a",
        "name": "John Doe",
        "address": {
          "country": "UA",
          "city": "Kyiv"
        }
      },
      "fields": {
        "card_number": "411111******1111"
      }
    }
  }
}

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

Options are configured on the Corefy side and affect how Corefy builds provider requests or processes responses.

Currently available options (2)

• send_recipient_and_sender_data - adds Sender/Recipient identification lists and address details to the payout request.
• customer_name_format - defines the order VisaNet Connect uses when splitting a single customer.name into first/last/middle parts for the recipient name.

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)

• RECIPIENT_FIRST_NAME -> customer.name (first part)
• RECIPIENT_LAST_NAME -> customer.name (last part)
• RECIPIENT_MIDDLE_NAME -> customer.name (middle part)
• RECIPIENT_ISSUE_COUNTRY_CODE -> customer.address.country (recipient identification fallback)
• SENDER_ISSUE_COUNTRY_CODE -> your business country (sender identification fallback)
• COMPANY_NAME -> your business (legal) name
• CARD_ACCEPTOR_NAME -> card acceptor (merchant) name
• CARD_ACCEPTOR_ADDRESS_COUNTRY -> card acceptor address country
• CARD_ACCEPTOR_ADDRESS_STATE -> card acceptor address state
• CARD_ACCEPTOR_ADDRESS_CITY -> card acceptor address city
• PROFILE_MCC -> your Merchant Category Code
• BUSINESS_APPLICATION_ID -> Visa Direct business application ID
• SOURCE_OF_FUNDS_CODE -> source-of-funds code
• POS_CONDITION_CODE -> point-of-service condition code
• PAN_ENTRY_MODE -> PAN entry mode code
• MOTO_ECI_INDICATOR -> MOTO/e-commerce indicator
• PAYMENT_FACILITATOR_ID -> payment facilitator ID
• PAYMENT_FACILITATOR_NAME -> payment facilitator name
• PAYMENT_FACILITATOR_SUB_MERCHANT_ID -> payment facilitator sub-merchant ID