Zeta Solution

Supports in this guide: Payments, Payouts

Provider website: zetasolution.io

What you need to do for start processing transactions (brief summary)

1. Choose account type
2. Get your credentials (from Zeta Solution)
3. Connect in Dashboard
4. Send an API request

Choose account type

Zeta Solution has a single account type that covers both directions:

• Provider account -> used for both payments (the customer pays with crypto on Zeta Solution's hosted invoice page) and payouts (crypto sent to a wallet address)

If you're not sure whether Zeta Solution fits your use case, confirm with your Corefy account manager.

Prerequisites: get from Zeta Solution

Sign up for a Zeta Solution merchant account, then generate and activate an API key in the Zeta Solution portal, API keys tab (see Zeta Solution's own API keys guide).

• Public Key -> Corefy field public_key -> the API key issued by Zeta Solution -> where to find: Zeta Solution portal, API keys tab. Sent on every request as the X-Processing-Key header.
• Secret Key -> Corefy field secret_key -> shown only once, right after the API key is activated -> where to find: Zeta Solution portal, API keys tab. Used to sign every request (X-Processing-Signature header) and to verify Zeta Solution's callbacks. Store it securely: if it's lost, the key has to be archived and a new one generated.
• API URL (optional) -> Corefy field api_url -> currently has a single option, Zeta Solution's production endpoint (https://app.zetasolution.io/api/v2) -> leave as default.

Use the Master API key for this connection. Zeta Solution signs callbacks only with the active Master key, and Corefy checks callbacks against the key you connect, so callbacks fail verification if you connect a Custom key.

If you restrict the API key to specific IP addresses in the Zeta Solution portal, ask your Corefy account manager which IPs to allow. If you leave the IP list empty, Zeta Solution accepts requests from any IP.

Make sure the crypto currencies/networks you plan to accept or pay out are enabled on your Zeta Solution merchant account before testing. Which of them are usable for a given connection depends on what's turned on for your account.

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8e3dbbb0-17af-4c9a-bedb-93bdac6900a2",
      "service": "zetasolution_eur_hpp",
      "currency": "EUR",
      "amount": 50,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com"
      }
    }
  }
}

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "bitcoin_eur_hpp",
      "currency": "EUR",
      "amount": 50,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com",
        "description": "VIP customer"
      }
    }
  }
}

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "0dde9e79-2c64-4703-adaf-93d710633401",
      "service": "bitcoin_usd",
      "currency": "USD",
      "amount": 50,
      "customer": {
        "reference_id": "cus_123"
      },
      "fields": {
        "wallet_id": "bc1qxy2kgdygjrsqtzq2n0yrf2493p83kkfjhx0wlh"
      }
    }
  }
}

Additional info

1. Callback routing. Zeta Solution sends payment and payout callbacks to a single URL per merchant account. The callback endpoint is /zetasolution/callback for both directions. Register it in the Zeta Solution portal under Settings -> Callbacks (see Zeta Solution's callback URL guide).
2. Callback authentication. Zeta Solution signs every callback with the X-Processing-Key/X-Processing-Signature headers (HMAC-SHA512 over the callback body with your Secret Key). Corefy verifies this automatically, so there's no separate callback secret to configure.
3. Sandbox. Enable Test mode only with Zeta Solution sandbox credentials. With Test mode on, Corefy sends requests to Zeta Solution's sandbox, and production credentials won't work there. To get sandbox access, contact Zeta Solution support.
4. USDT networks. For services priced in USDT (tether_trc20_usdt_hpp, tether_erc20_usdt_hpp), the invoice is created directly in the network-specific asset (TRC20 or ERC20), so the customer pays on the network the service names.
5. No destination tag/memo on payouts. Corefy doesn't send a tag/memo with Zeta Solution payouts. Check with your account manager before paying out to destination wallets that require one (for example, some XRP exchange addresses).
6. No reconciliation. Payment and payout statuses are updated only through callbacks. Reconciliation isn't supported for this connector.

FAQ / Troubleshooting

• INVALID_DETAILS / payment rejected -> customer.email is missing; it's required for every Zeta Solution payment
• Validation error on customer.reference_id -> it's required whenever a customer object is sent, which is always the case for Zeta Solution payments and payouts
• Callbacks don't arrive -> check that /zetasolution/callback is registered in the Zeta Solution portal under Settings -> Callbacks
• Payout rejected with a no-customer error -> customer.reference_id is missing; a payout without a customer is rejected before it reaches Zeta Solution
• Connection test fails / invalid credentials -> check that the Public Key and Secret Key belong to the same active API key, and that Test mode matches the environment the keys were issued for
• Callbacks rejected with an invalid signature -> make sure you connected the active Master API key, since Zeta Solution signs callbacks only with it
• A currency/crypto pair I expect isn't available -> confirm it's enabled on your Zeta Solution merchant account, then check the Dashboard's Currency / Features selector for this connection. For payouts, also check that the crypto has a balance on your Zeta Solution account.
• Not sure which account type to use? -> ask your Corefy account manager