⚠️ Important: This article applies to: Properties using the Alliants Experience Platform (AXP) with Oracle OHIP integration
Overview
During or shortly after a go-live or an update of integrations, some properties may notice that credit card charges processed through AXP are not appearing in the Property Management System (PMS). This article explains why this happens, how to spot it, and how to prevent it.
Why This Happens
AXP maps each accepted card type (e.g. Visa, Mastercard, Amex) to a corresponding code in your PMS. Oracle OHIP uses two separate identifiers for each card:
Identifier | Purpose | Example (Visa) |
Payment Method Code | Identifies the payment method in OHIP |
|
Card Type | A secondary classification used in transaction flexfields |
|
These are easy to mix up because both are short codes associated with the same card brand.
If the Card Type value (VA) is used where the Payment Method Code (VI) is expected, AXP cannot match the transaction to the correct payment method in OHIP — and the charge will not post.
How to Tell If This Is the Problem
You may be experiencing this issue if:
Credit card payments complete successfully on the guest-facing side, but do not appear in the PMS.
The issue affects a specific card type (e.g. only Visa transactions are missing, while Mastercard posts correctly).
The issue appeared immediately at go-live or after a configuration update.
If you are seeing any of the above, please contact the Alliants support team and provide an example booking or transaction reference so we can investigate quickly.
How to Prevent This
For project managers and IT teams involved in setting up or reviewing a property's AXP configuration before go-live:
1. Confirm payment method codes with your OHIP
Before finalising the AXP payment configuration, ask your Oracle OHIP team to provide the payment method codes configured in your OHIP instance for each accepted card brand. These are typically two-letter codes (e.g. VI, MC, AX) and must match exactly what is in OHIP.
2. Do not use card type values in place of payment method codes
Card types are a separate concept used inside transaction records. Even though they may look similar (e.g. VA vs VI), they serve different purposes and are not interchangeable in the payment mapping configuration.
3. Request a payment config review as part of go-live sign-off
Ask the Alliants deployment team to verify the payment method mapping against your live OHIP configuration before your go-live date. This is a standard step we recommend for all new properties or properties just did an update on PMS or OHIP.
4. Test each card type before go-live
Run a test transaction for each accepted card brand in a staging environment and confirm the charge appears correctly in the PMS. Do not assume that a successful guest-facing payment means the PMS has received it.
Reference: Common Payment Method Codes
The following codes are standard across most OHIP configurations, but always confirm with your OHIP as these can be customised per property:
Card Brand | Typical Payment Method Code |
Visa |
|
Mastercard |
|
American Express |
|
Need Help?
If credit card charges are not posting to your PMS, contact the Alliants support team with:
The property name and environment URL (the URL you log in Alliants Experience Team)
An example booking reference or transaction date
Which card types are affected