Alphapo

Supports in this guide: Payments, Payouts

Provider website: alphapo.net

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

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

Choose account type

Alphapo has a single account type that covers both directions:

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

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

Prerequisites: get from Alphapo

Sign up and complete verification at alphapo.net, then generate an API key in your Alphapo merchant back-office (see Alphapo's own Initial setup guide).

• Public Key -> Corefy field public_key -> the API key identifier issued by Alphapo -> where to find: Alphapo merchant back-office, API keys section. Sent on every request as the X-Processing-Key header.
• Secret Key -> Corefy field secret_key -> shown once when the API key is generated -> where to find: Alphapo merchant back-office, API keys section. Used to sign every request (X-Processing-Signature header) and to verify Alphapo's callbacks - store it securely, it can't be retrieved again later.
• API URL (optional) -> Corefy field api_url -> currently has a single option, Alphapo's own endpoint (https://app.alphapo.net/api/v2) -> leave as default unless your account manager tells you otherwise.

Make sure the crypto currencies/networks you plan to accept or pay out are enabled on your Alphapo merchant account before testing - Alphapo's supported cryptocurrencies list covers 40+ assets across multiple blockchain networks (BTC, ETH, USDT/USDC on several networks, LTC, XRP, and others), and which of them are actually usable on a given transaction depends on what's turned on for your account.

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "bitcoin_eur_hpp",
      "currency": "EUR",
      "amount": 50,
      "customer": {
        "email": "johnsmith@gmail.com"
      }
    }
  }
}

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "bitcoin_eur_hpp",
      "currency": "EUR",
      "amount": 50,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com"
      }
    }
  }
}

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "service": "bitcoin_eur",
      "currency": "EUR",
      "amount": 50,
      "customer": {
        "reference_id": "cus_123"
      },
      "fields": {
        "wallet_id": "bc1qxy2kgdygjrsqtzq2n0yrf2493p83kkfjhx0wlh"
      }
    }
  }
}

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "service": "bitcoin_eur",
      "currency": "EUR",
      "amount": 50,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith"
      },
      "fields": {
        "wallet_id": "bc1qxy2kgdygjrsqtzq2n0yrf2493p83kkfjhx0wlh"
      }
    }
  }
}

Additional info

1. Callback authentication. Alphapo signs every callback with the same X-Processing-Key/X-Processing-Signature headers used for outgoing requests (HMAC over the callback body using your Secret Key); Corefy verifies this automatically - there's no separate callback secret to configure in Alphapo's back-office.
2. Currency conversion on payouts. If the payout's settlement currency differs from the destination crypto asset, Alphapo performs the conversion on its side (via the route implied by the service code) - the exchange isn't always a direct conversion and may go through intermediate pairs, which can affect the exact amount received.
3. Dynamic currency routing. Unlike connectors with a fixed currency list, which crypto/fiat pairs are available for a given Alphapo account is resolved at connection time from what's actually enabled on that account - if a service code you expect to use is missing after connecting, check the Currency / Features selector in the Dashboard connection form or contact your account manager.

FAQ / Troubleshooting

• INVALID_DETAILS / payment rejected -> customer.email is missing; it's mandatory for every Alphapo payment
• Payout rejected with no customer error -> customer.reference_id is missing; a payout without a customer is rejected before it reaches Alphapo
• A currency/crypto pair I expect isn't available -> confirm it's enabled on your Alphapo merchant account and reflected in the Dashboard's Currency/Features selector for this connection
• Invalid signature on callback -> verify the Secret Key used to connect matches the API key currently active in your Alphapo account
• Not sure which account type to use? -> ask your Corefy account manager