Skip to content

Logo

Confirmo

Supports in this guide: Payments | Payouts

Provider website: confirmo.net


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

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

Choose account type

Confirmo can be connected in different ways (depending on your needs):

  • If you do redirect payments (customer is redirected to Confirmo's hosted crypto checkout) -> choose Provider account
  • If you do crypto payouts -> choose Provider account

If you are not sure which one to use, confirm with your Corefy account manager.


Prerequisites: get from Confirmo

Get the following values for your Confirmo project/account:

  • API Token -> Corefy field api_token -> example: cnfY0urAp1T0k3nV4lue -> where to find: Confirmo backoffice / issued by Confirmo manager. Bearer token sent with every request to the Confirmo API.
  • Merchant ID -> Corefy field merchant_id -> example: my-confirmo-account -> this one is not issued by Confirmo: it is an identifier you choose yourself to name this connection inside Corefy. It is used as the account's external ID and as the prefix of the deposit accounts created for each balance currency.

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

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • Merchant ID -> merchant_id
  • API Token -> api_token
  • Currency / Features -> Choose Currency and Features. You can set these parameters according to available currencies and features for your Confirmo account, but it is necessary to check details of the connection with your Corefy account manager.

Success

You have connected Confirmo Provider account!


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": "8f3a2c10-1f2b-4a1e-9f77-2b5c9d4e7a01",
      "service": "crypto_aggregated_eur_hpp",
      "currency": "EUR",
      "amount": 100
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8f3a2c10-1f2b-4a1e-9f77-2b5c9d4e7a01",
      "service": "crypto_aggregated_eur_hpp",
      "currency": "EUR",
      "amount": 100,
      "customer": {
        "reference_id": "c1d2e3f4-5a6b-47c8-9d0e-1f2a3b4c5d6e"
      }
    }
  }
}

The customer is optional: when customer.reference_id is sent, it is passed to Confirmo as the customer profile ID, so repeated payments from the same payer are grouped on the provider side. No other customer field is sent to Confirmo for payments.


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


Refunds

Confirmo does not support refunds for payments.


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

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

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

  • Merchant ID -> merchant_id
  • API Token -> api_token

Success

You have connected Confirmo Provider account!


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": "4b7e1d93-6c2a-4f58-8a10-9e0b3c7d2f44",
      "service": "tether_trc20_usdt",
      "currency": "USDT",
      "amount": 100,
      "fields": {
        "wallet_id": "TJRyWwFs9wTFGZg3JbrVriFbNfCug5tDeC"
      }
    }
  }
}

Payout - MAX

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "4b7e1d93-6c2a-4f58-8a10-9e0b3c7d2f44",
      "service": "tether_trc20_usdt",
      "currency": "USDT",
      "amount": 100,
      "customer": {
        "reference_id": "c1d2e3f4-5a6b-47c8-9d0e-1f2a3b4c5d6e"
      },
      "fields": {
        "wallet_id": "TJRyWwFs9wTFGZg3JbrVriFbNfCug5tDeC"
      }
    }
  }
}

fields.wallet_id is the destination crypto address and is required: it is sent to Confirmo as the payout address. The payout service must match the crypto network of that address. customer.reference_id is optional and is passed as the customer profile ID.


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.

Both options are set per payout service, on the payout route.

Currently available options (2)

  • fee_payment_mode - who pays the Confirmo fees for the payout
  • use_provider_debited_amount - whether the amount debited by Confirmo is applied as the actual payout amount instead of the requested amount
fee_payment_mode

What it does: sends feePaymentMode to Confirmo with the payout, which decides who covers the processing and network fees. When the option is left empty, Corefy keeps the previous behaviour and sends the legacy treatAsGrossAmount: true instead, so the fees are taken from the requested amount and the recipient gets less than the requested amount. When to use: set it to MERCHANT when the recipient must receive exactly the requested amount and the fees are charged on top, taken from your Confirmo balance. Default: not set (legacy treatAsGrossAmount: true behaviour) Allowed values: MERCHANT (merchant pays all fees), RECIPIENT (recipient pays all fees), NETWORK_FEE_RECIPIENT (merchant pays the processing fee, recipient pays the network fee)

use_provider_debited_amount

What it does: on payout reconciliation and callback, applies the amount actually debited from your Confirmo balance (debitedAmount, less fee) as the actual payout amount, instead of the requested amount. The response value is used only when its fee currency matches the payout currency. The debited amount itself is reported in the payout statement regardless of this option, so turning the option on changes only the actual amount of the payout. When to use: enable it together with fee_payment_mode, where the debited amount and the requested amount differ because of the fees. Default: false (the requested amount is reported as the actual amount) Allowed values: true / false


Refunds

Confirmo does not support refunds for payouts.


Additional info

  1. Payouts are created in two steps on Confirmo's side: Corefy creates the payout and then immediately confirms it. Confirmo's own flow leaves the payout unconfirmed so a merchant can review the exchange rate first; that step does not fit the Corefy payout flow, so payouts are confirmed automatically and cannot be cancelled between the two steps.

  2. Callbacks are supported for both payments and payouts. The notification URL is generated and sent by Corefy with every invoice and payout, so there is nothing to configure on the Confirmo side. A callback triggers a reconciliation request, and the status from that request is what is applied to the transaction.

  3. Payout routes are matched to Confirmo's crypto payment methods by the route's external ID, which must be one of the method IDs returned by GET /api/v3/crypto-payment-methods for your API token (for example, TRON-BLOCKCHAIN-MAINNET-USDT-STANDARD). A payout whose route external ID is not in that list is rejected before any request is sent to Confirmo.

  4. Deposit account balances are read from Confirmo and created per currency, for the currencies that your payout routes use.

  5. Confirmo has no test environment; the same https://confirmo.net/api base URL is used for production and testing.


FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify the API Token is the one issued for this Confirmo account and that it has not been rotated in the Confirmo backoffice
  • This payout method is not available at the moment -> the route's external ID is not in Confirmo's current crypto payment method list; ask your Corefy account manager to re-check the route configuration
  • Currency or service is not supported -> confirm the crypto assets enabled for payouts on your Confirmo account and the services configured in Corefy
  • The recipient received less than the requested amount -> set the fee_payment_mode option to MERCHANT on the payout route
  • Not sure which account type to use? -> ask your Corefy account manager

Question

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