Overview#
Cross Module E-pass is designed to provide flexibility and convenience for clients who want a single E-pass to cover multiple airport service modules. Key benefits include:Multi-module usage: One E-pass can be redeemed across Lounge, Set Meal, and Coupon modules.
Maximized entitlement value: Avoids wasted benefits when a specific module is unavailable at an airport.
Simplified user experience: Users only need a single pass for multiple types of services.
Enhanced client appeal: Supports flexible product design for partners, e.g., offering “1 airport service access” without exposing individual modules.
Scope and Limitations#
Currently, E-pass only supports cross-module usage among the following modules:| Module | Description |
|---|
| 1 | Lounge |
| 3 | Set Meal |
| 4 | Coupon |
Clients can combine any subset of the supported modules into a single program (e.g., Lounge + Set Meal, Lounge + Coupon, or all three). The final combination must be confirmed with DP before project launch.Other modules are not supported for Cross Module E-pass at this stage.
Issue An Cross Module E-pass#
For Cross Module E-pass, set {module} to crossModule:Unlike a standard single-module E-pass, Cross Module E-pass includes an additional field allowedModules to indicate which modules the E-pass can be used for. Example:This field is returned only for Cross Module E-pass. It helps clients and front-end systems display the available modules for redemption.Create E-pass Order - Request
module field must be 0 to indicate Cross Module.
{
"module": 0,
"clientUserId": "3EF5D065-76F8-4D3E-801A-B329D15F461A",
"extra": {
"firstName": "DragonPass",
"lastName": "DragonPass",
"activationDate": "2025-12-31T23:59:59+00:00",
"expirationDate": "2028-12-31T23:59:59+00:00",
"availableUsages": 1,
"allowedResources": {
"resourceIds": []
}
}
}
Create E-pass Order - Cross Module - Response
{
"code": 0,
"data": {
"status": 1,
"module": 0,
"category": 1,
"clientUserId": "3EF5D065-76F8-4D3E-801A-B329D15F461A",
"orderId": "DP00000000000001",
"orderCreatedDate": "2024-12-31T00:00:00+00:00",
"orderCancelledDate": null,
"extra": {
"ePassId": "1788000066668888",
"ePassStatus": 1,
"firstName": "DragonPass",
"lastName": "DragonPass",
"activationDate": "2025-10-31T23:59:59+00:00",
"expirationDate": "2028-12-31T23:59:59+00:00",
"availableUsages": 1,
"usedUsages": 0,
"allowedResources": {
"resourceIds": []
},
"allowedModules": [
1,
3,
4
]
}
}
}
Resource Search & Usage Order Query#
A Cross Module E-pass only means that the E-pass can be used across multiple modules. It does not change the existing logic for resource search or usage order queries:Resource Search
Please keep the current process unchanged. You still need to specify the target module when searching for resources.
The Cross Module E-pass does not automatically return resources from all modules.
Usage Order Attribution
Once a E-pass is redeemed, the generated usage order will be attributed to the actual module of the redeemed resource.
In other words, the order’s module will reflect the real service used (e.g., Lounge, Set Meal, Coupon) and will no longer be 0.
Assume a Cross Module E-pass program is configured with:To find lounges → search with module = 1
To find set meals → search with module = 3
Redemption & Order ResultIf the user redeems a Lounge → The usage order will be created with module = 1
If the user redeems a Set Meal → The usage order will be created with module = 3