Skip to content

TomPayment

Supports in this guide: Payments

Note

No independently verifiable public website could be confirmed for this provider - none is listed in OFT. Contact your account manager for onboarding details.

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

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

Prerequisites: get from TomPayment

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

  • Account ID -> Corefy field account_id.
  • Password -> Corefy field password.
  • Access key -> Corefy field access_key.
Payments processing (connect H2H Merchant account, create payment-invoice)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • Account ID
  • Password
  • Access key
  • Currency / Features -> choose values available for your account

Success

You have connected TomPayment H2H Merchant 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. TomPayment may return a 3D Secure challenge redirect depending on the card.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "0a21ab74-0d33-4383-a927-edbba3951e4e",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "1b32bc85-1e44-4494-a938-fecca4062f5f",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Doe",
        "email": "test@example.com"
      }
    }
  }
}

Important

  • customer.name is sent to TomPayment only as the card's own embossed cardholder name (via the usual cardholder-name resolution), not directly from customer.name.
  • customer.email is optional pass-through; if missing, it's simply not sent. No Constants are configured for this connector.

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

  • three_ds_type -> optional, enum (Soft 3DS, Hard 3DS) - which 3D Secure mode TomPayment should apply to the transaction.

Refunds

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

Additional info

  1. No reconciliation on this connector - TomPayment statuses arrive only via the asynchronous callback; there is no active status request available.
  2. No recurring - this connector does not support saving/charging a token through Corefy.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify the Account ID, Password and Access key
  • Payment stuck pending with no status update -> this connector has no active status request; confirm your callback endpoint is reachable and correctly configured
  • Refund fails with multiple attempts -> only one refund per payment is allowed

Question

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