WZRD PAY

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Commerce Account
• API Key
• Key for Callback (optional)
• API URL
• Send Metadata (optional)
• 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. WZRD PAY may return a 3D Secure challenge redirect depending on the card.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "1a2b3c4d-5e6f-4a7b-8c9d-0e1f2a3b4c5d",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10
    }
  }
}

This connector also supports EUR, KZT, TRY, PLN, AUD.

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "2b3c4d5e-6f7a-4b8c-9d0e-1f2a3b4c5d6e",
      "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",
          "city": "New York"
        }
      }
    }
  }
}

customer is entirely optional and is only used to enrich 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 Constants are configured for this connector.

Options

• ignore_callback -> optional, boolean - for cascading to work correctly, excludes finalizing the payment from the asynchronous callback; Corefy then relies only on an active status request (reconciliation) to finalize it.
• save_provider_instant_token -> optional, boolean - if WZRD PAY's response includes an instant token, Corefy stores it; confirm with your account manager whether a follow-up charge using this token is available for your account.
• generate_random_customer_data -> optional, boolean - if enabled and customer is missing from your request, Corefy automatically fills it in with generated placeholder data instead of sending nothing.
• transliterate_customer_data -> optional, boolean - transliterates customer fields to Latin before sending them to WZRD PAY.
• transliterate_card_holder -> optional, boolean - transliterates the card's embossed holder name to Latin before sending it to WZRD PAY (independent of the customer transliteration above).
• set_description -> optional, boolean - sends your transaction descriptor as the payment's description, instead of leaving it blank.
• duplicate_original_resolution -> optional, boolean - if Corefy's own resolution mapping can't classify WZRD PAY's response, falls back to reporting WZRD PAY's original resolution code instead of leaving it blank.

Refunds

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

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Commerce ID
• API Key
• Secret Key for Callback
• API URL (optional)
• Send Metadata (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": "3c4d5e6f-7a8b-4c9d-8e0f-1a2b3c4d5e6f",
      "service": "payment_card_eur",
      "currency": "EUR",
      "amount": 10,
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

Corefy doesn't restrict currencies for this flow in advance - available currencies depend entirely on what's enabled for your WZRD PAY account; confirm with your account manager.

Payout - MAX

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "4d5e6f7a-8b9c-4d0e-8f1a-2b3c4d5e6f7a",
      "service": "payment_card_eur",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith"
      },
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

customer is entirely optional - name, when sent, is forwarded as the receiver's name.

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_description -> optional, boolean - sends your transaction descriptor as the payout's description, instead of leaving it blank.
• allow_conversion -> optional, boolean - allows WZRD PAY to convert the payout amount to a different settlement currency on their side, instead of rejecting it when the requested currency isn't directly available.