Aera

Configure Aera payment provider with Omnium for card and invoice payments.

Aera Integration with Omnium

Omnium supports Aera payment processing with two distinct payment methods:

  • Aera - Card payment processing
  • Aera Invoice - Invoice-based payments (separate configuration)

Supported Features

  • Authorize payments via in-store app integration
  • Capture payments (with automatic fallback if authorization expires)
  • Cancel payments / release authorization
  • Credit/Refund payments with item-level granularity
  • Get Details - Retrieve comprehensive payment information
  • Import Payments - Sync payment history from Aera

Setup Instructions

Configuration Path

  1. Navigate to: Configuration > Settings > Payment > Payment Types > "..." > Add

  2. Fill out the required fields as outlined below.


Required Fields

FieldDescriptionValue
Unique Payment NameThe unique identifier for the Aera payment method.Aera
Payment ServiceThe name of the payment service used for this configuration.Aera
Provider NameSpecifies which provider to use for processing the payment.Aera
Display NameThe name shown in the Omnium interface.Aera or your preferred name
Base URLThe Aera API endpoint URL.See Base URL Options
API TokenYour Aera authentication token.Your API Token from Aera
Vue TemplateThe template for payment method integration.aera-payment

Authentication Properties

Add these as custom properties in the payment configuration:

PropertyDescription
UsernameYour Aera OAuth2 username
PasswordYour Aera OAuth2 password

Base URL Options

EnvironmentBase URL
Test/Staginghttps://api-staging.aerahost.com
Productionhttps://api.aerahost.com

Merchant ID Configuration

Aera supports flexible merchant ID configuration with two options:

Option 1: Global Merchant ID

Set the Merchant ID field in the payment configuration. This will be used for all stores.

Option 2: Store-Level Merchant ID

Add a property named AeraMerchantId to individual stores. This allows different stores to use different Aera merchant accounts.

Configuration Priority:

  1. If Merchant ID is set in payment settings, it is used for all stores
  2. If Merchant ID is empty, the system looks for the AeraMerchantId property on the store
  3. If neither is configured, an error is thrown

Store-level merchant IDs are only checked when the global Merchant ID is not set in the payment configuration.


Additional Configuration

SettingDescriptionDefault
Display in CartShow Aera as a payment option in the cart interface.true
Get Details From ProviderEnable fetching real-time payment details from Aera.true
Valid On MarketsRestrict to specific markets. Leave empty for all.All markets
Valid For StoresRestrict to specific stores. Leave empty for all.All stores

Supported Operations

OperationAera (Card)Aera InvoiceNotes
AuthorizeYesNoIn-store app-based authorization
CaptureYesYesFull capture with auto-fallback
Partial CaptureNoYesInvoice supports partial activation
CancelYesYesFull authorization cancellation
Release Remaining AuthYesYesRelease partial authorization
RefundYesYesFull or partial with item-level detail
Get DetailsYesNoComprehensive payment breakdown
Import PaymentsYesNoSync payment history
In-Store RegistrationYesNoCreates payment session with app URL
Check StatusYesYesPayment status retrieval

Special Features

Automatic Capture Fallback

When capturing a payment, if the authorization has expired, Aera automatically attempts a Collect transaction instead. This provides resilience for orders with longer fulfillment times.

Flow:

  1. Capture is attempted against the authorization
  2. If authorization has expired, system automatically tries Collect
  3. If Collect also fails, the operation returns an error

This behavior is automatic and requires no configuration.

Get Payment Details

When Get Details From Provider is enabled, you can retrieve comprehensive payment information including:

  • Authorization details (amount, code, expiration)
  • Capture history (multiple captures tracked individually)
  • Refund history (individual refund transactions)
  • Cancellation tracking
  • Masked card number (last 4 digits)
  • Payment scheme and card type

Import Payment History

Aera supports importing complete payment history for reconciliation purposes. This creates payment records for all transactions:

Aera Transaction TypeOmnium Transaction Type
CardAuthorizeAuthorization
CaptureCapture
VoidRelease Remaining Authorization
RefundCredit

Adding Payments via API

Payments can be added to orders programmatically using the endpoint:

POST /api/Orders/{orderId}/AddPayments

Important: Set the payment status to Processed and match the payment method name with your configuration.

Transaction ID Handling:

  • If the Transaction ID is a GUID format, it's treated as a payment reference from Aera
  • Other formats are treated as transaction IDs

Aera Invoice

Aera Invoice is a separate payment method for invoice-based payments. It requires its own configuration.

Invoice Configuration

FieldValue
Payment ServiceAeraInvoice
Provider NameAera
Vue Templateaera-payment

Invoice-Specific Operations

  • Activate Invoice - Full invoice activation (capture)
  • Partially Activate Invoice - Capture specific items
  • Credit Invoice - Return specific items
  • Adjust Invoice - General credits without item-level detail

In-store payment registration is not supported for Aera Invoice.


Error Handling

Aera errors are displayed on the order in the Errors section. All operations use idempotency keys to prevent duplicate processing.

Common Issues

IssuePossible CauseSolution
Authentication failedInvalid credentialsVerify Username, Password, and API Token
Merchant ID not foundMissing configurationSet Merchant ID in settings or on store
Capture failed after retryAuthorization expired and Collect also failedContact Aera support
Invalid payment referenceWrong format in API callUse GUID for payment reference, other for transaction ID

Configuration Reference

Payment Service Values

  • Aera Card: Aera
  • Aera Invoice: AeraInvoice

Store Property

  • AeraMerchantId - Store-level merchant ID override

API Authentication

OAuth2 Password Grant flow using configured Username and Password credentials.