https://{baseUrl}/V2/{customerID}/{action}hotelID (property identifier) and hotelIDType.baseUrlFor test in Europe use: service.stage.payengine.sihot.com
For test in Australia use: service.stage.payengine.ap.sihot.cloud
For production refer to the project management of the implementation.
hotelIDTypeThe parameter hotelIDType is a string that indicates the type of identifier used in the hotelID field. Supported values include, but are not limited to:
SIHOT.PMS: The hotelID is a SIHOT PMS hotel number.SIHOT.POS: The hotelID refers to a POS outlet number.SiteminderID: The hotelID refers to a Siteminder integration identifier.In project-specific implementations where the correct
hotelIDTypeis unclear, partners must consult SIHOT support to determine the appropriate value.
Please note: For each client integration, the hotelIDType is typically a fixed and predefined value that should not be changed dynamically across requests.
| returnCode | Description |
|---|---|
| 0 | Success |
| 1 | Transaction declined |
| 2 | Declined for security reasons |
| 3 | Call card issuer |
| 4 | Invalid/missing request data |
| 5 | System error |
| 6 | Configuration error |
| 7 | Function not implemented |
| -1 | Unknown/un-categorized error |
If returnCode is not 0, returnText, returnCodeSP, and returnTextSP provide extra details.
| cardType | cardTypeCode | Card Brand |
|---|---|---|
| 1 | americanExpress | American Express |
| 2 | dinersClub | Diners Club |
| 3 | masterCard | MasterCard |
| 4 | visa | Visa |
| 5 | discover | Discover |
| 6 | jcb | JCB |
| 7 | enRoute | enRoute |
| 8 | ecCard | EC Card |
| 9 | red6000 | Red6000 |
| 10 | vierB | VierB |
| 11 | other | Other |
| 12 | jelmoli | Jelmoli |
| 13 | vPay | V Pay |
| 14 | unionPay | UnionPay |
| 15 | mirrussia | Mir (Russia) |
| 16 | eftpos | Eftpos |
Provider references (e.g. spayengine) are configured per project. If you require multiple merchant accounts (e.g., for MOTO and eCommerce), consult integration support.
The CustomerID is a unique ID of a customer in the context of SIHOT.PAYENGINE. This ID is provided per customer from the integrations team once a customer is onboarded.
Several requests contain an optional string field named supportedFeatures.
This field can include features that need to be considered. Currently it support this features:
| Feature | Description |
|---|---|
| surcharge | If this is set, then SIHOT.PAYENGINE will automatically apply a surcharge amount to the transaction before triggering the transaction on payment provider side. The surcharge amount is configurable per SIHOT.PAYENGINE customer. |
| tip | If this is set, then payment providers, where tip functionality has been integrated, can automatically add an extra amount as tip. |
If multiple features have to be used, they can be separated by a comma in the supportedFeatures field (e.g surcharge,tip to use the SIHOT.PAYENGINE surcharge handling and to allow tips).
This request is currently included in:
tip is not supported for authorizations)tip is not supported for authorizations)