Skip to content

Logo

Match2Pay

An effective crypto processor for your business ensuring seamless transactions for your clients and unmatched convenience.

Supports in this guide: Payments, Payouts

Provider website: match2pay.com

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

  1. Get your credentials (from Match2Pay)
  2. Connect in Dashboard
  3. Send an API request

Prerequisites: get from Match2Pay

Contact your Match2Pay account manager to get your account verified and receive the following credentials.

  • API token -> Corefy field api_token.
  • API secret -> Corefy field api_secret.

Bitcoin, Ethereum, Tron, Binance Coin, Tether (ERC20/BEP20/TRC20), USD Coin (ERC20/BEP20/TRC20) - settled in USD, EUR, GBP, or CHF.

Payments processing (connect Provider account, create payment-invoice)

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • API token
  • API secret
  • Currency / Features -> choose the crypto/currency combinations available for your account
  • Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected Match2Pay Provider account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice and redirects the customer to a Match2Pay-hosted crypto checkout page. No customer fields are used by this connector at all.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6be05631-8710-4b14-a369-1928a2b70eda",
      "service": "bitcoin_usd_hpp",
      "currency": "USD",
      "amount": 100
    }
  }
}

Important

  • This connector does not use any customer fields - only amount/currency/service reach Match2Pay.
  • Crypto amounts can drift between invoice creation and actual payment (price fluctuation, manual wallet transfers). If the amount the customer actually sent is less than requested, Corefy keeps the payment pending (with message "Partial amount cannot be processed") instead of marking it successful - unless allow_split_payments is enabled (see Options below).

Extended request (MAX)

Why add extra fields (typical reasons): - Include optional fields required by your specific flow

This connector has no optional request fields beyond MIN - every other supported crypto/currency combination is just a different service value (see the full list in Additional info).

Options

  • allow_split_payments -> optional, boolean - when enabled, a payment is accepted as successful even if the customer sent a smaller crypto amount than requested; when disabled (default), an underpaid transaction is left pending instead of auto-completed.

Refunds

Match2Pay does not support refunds.

Payouts processing (connect Provider account, create payout-invoice)

Connect Provider account in Corefy Dashboard

Uses the same Provider account connected above - no separate connection step.

First request to Corefy API (MIN)

What it does: creates a payout-invoice and sends crypto to the given wallet address.

Payout - MIN

POST /api/payout-invoices 

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "15da57fd-f4bc-4084-91f8-0a5d96e55b24",
      "service": "bitcoin_usd",
      "currency": "USD",
      "amount": 101.98,
      "customer": {
        "reference_id": "cus_123"
      },
      "fields": {
        "wallet_id": "1Lbcfr7sAHTD9CgdQo3HTMTkV8LK4ZnX71"
      }
    }
  }
}

Important

  • fields.wallet_id (the destination crypto address) is required.
  • Payouts are only available for Bitcoin, Ethereum, Binance Coin, Tether (ERC20/BEP20/TRC20), and USD Coin (ERC20/BEP20) - unlike Payments, Tron and USD Coin TRC20 have no payout route.

Extended request (MAX)

Why add extra fields (typical reasons): - Include optional fields required by your specific flow

This connector has no optional request fields beyond MIN.

Additional info

  1. No active reconciliation on either flow - both Payments and Payouts are confirmed only via Match2Pay's asynchronous callback; there is no active status request for this connector.
  2. No recurring - this connector does not support saving/charging a token through Corefy.
  3. Callback signature quirk - Match2Pay signs success callbacks correctly, but callbacks with a DECLINED status are known to arrive with an invalid/missing signature; Corefy accepts DECLINED callbacks regardless of signature validity to work around this.
  4. Full service matrix - services follow the pattern {crypto}_{currency}_hpp for Payments (e.g. tether_erc20_eur_hpp) and {crypto}_{currency} for Payouts (e.g. tether_erc20_eur), across Bitcoin, Ethereum, Tron (Payments only), Binance Coin, Tether (ERC20/BEP20/TRC20), and USD Coin (ERC20/BEP20, plus TRC20 for Payments only) - each combined with USD, EUR, GBP, or CHF.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify the API token and API secret, and that Test Mode matches the credential environment
  • Currency or service is not supported -> confirm allowed currencies/features in your Match2Pay account and in Corefy
  • Payment stuck in pending after the customer paid -> the customer may have sent less than the requested crypto amount; enable allow_split_payments if underpaid transactions should still complete
  • Payout fails -> fields.wallet_id must be a valid address for the selected cryptocurrency; confirm the service supports a payout route (Tron and USD Coin TRC20 do not)
  • Refund fails -> Match2Pay does not support refunds through Corefy

Question

Still looking for help connecting your Match2Pay account? Please contact our support team!