Skip to content

Axcess Merchant Services

Axcess Merchant Services

Merchant account solutions to fit your business model. Greater choice, flexibility and bespoke merchant account arrangements.

Supports in this guide: Payments

Provider website: axcessms.com

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

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

Prerequisites: get from Axcess Merchant Services

Contact your Axcess Merchant Services account manager (via the website or the support hotline) to get your account verified and receive the following credentials:

  • Entity ID -> Corefy field entity_id.
  • Access Token -> Corefy field access_token.

Note

If you need to whitelist IPs on Axcess Merchant Services's side, ask your account manager and provide Corefy's IP list from the integration docs.

Payments processing (connect H2H Merchant account, create payment-invoice)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

Open Axcess Merchant Services in the provider directory and press Connect at Axcess Merchant Services Provider Overview page in the New connection section. Choose H2H Merchant account.

Step 2 - Fill in fields and select settings

  • Entity ID
  • Access Token
  • Test Mode -> (enable if you are using sandbox credentials)
  • Currency / Features -> choose values available for your account

Success

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

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "4a1b2c3d-5e6f-4a7b-8c9d-1e2f3a4b5c6d",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "5b2c3d4e-6f7a-4b8c-8d0e-2f3a4b5c6d7e",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "first_name": "John",
        "last_name": "Doe",
        "email": "john.doe@example.com",
        "address": {
          "country": "GB",
          "city": "Leeds",
          "street": "Main street 1",
          "post_code": "LS2 9DF"
        }
      }
    }
  }
}

Important

  • customer fields (name, email, billing address) are optional and only forwarded to Axcess Merchant Services when the include_customer_data option is enabled.
  • Your own merchant details (company name, city, country, IBAN - taken automatically from your Corefy merchant profile) are only sent as sender data when the include_sender_data option is enabled.
  • Full browser details (accept header, color depth, Java/JavaScript support, language, screen size, timezone) are always collected and sent automatically for 3D Secure processing - no customer fields are required for this.

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

  • include_sender_data -> optional, boolean - additionally sends your own merchant profile data (company name, city, country, IBAN) as sender information.
  • include_customer_data -> optional, boolean - additionally sends customer billing address, name, and email.
include_sender_data

What it does: sends your Corefy merchant profile's company name, city, country, and IBAN to Axcess Merchant Services as sender information on the transaction.

When to use: when Axcess Merchant Services or your compliance requirements call for sender identification on transactions.

Default: false

Allowed values: true / false

include_customer_data

What it does: sends customer.address (street, city, post code, country), customer.first_name/last_name, and customer.email to Axcess Merchant Services.

When to use: when Axcess Merchant Services or your compliance requirements call for customer billing details on transactions.

Default: false

Allowed values: true / false

Note

If you are not sure which value to select, please contact our support team!

Refunds

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

Recurring

Axcess Merchant Services supports saving a token on the first payment (when your Corefy request enables tokenization) and charging it later for recurring/merchant-initiated transactions, without the cardholder re-entering card details.

Additional info

  1. Active reconciliation is available - payments support an active status request in addition to any asynchronous callback.
  2. CVV is always required - non-CVV payments are not supported.
  3. No dedicated 3D Secure version control - Axcess Merchant Services manages the 3DS flow using the browser details Corefy sends automatically.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify the Entity ID and Access Token for the selected environment (test_mode)
  • Currency or service is not supported -> confirm allowed currencies/features in your Axcess Merchant Services account and in Corefy
  • Missing customer/sender details on the provider side -> enable include_customer_data and/or include_sender_data
  • Refund fails with multiple attempts -> only one refund per payment is allowed

Question

Still looking for help connecting your Axcess Merchant Services account? Please contact our support team!