...
The payments are facilitated from b4checkin's b4payment service to integrated payment gateways, such as Authorize.NET, Shift4, FuseBox, etc. Upon successful transaction, the payment results are posted in the PMS. Currently, TransForm integrates with the following property management systems (PMS'): Agilysys Visual One, Agilysys LMS, Infor HMS and Opera by Oracle.TransForm supports PMS and custom /wiki/spaces/BTD/pages/115277876. Regular payment types are the ones that have predefined template which info guest has to fill for submitting the payment. Custom payment types are the ones that can be customized which fields guest has to fill and which are required or optional. The table below displays the supported payment types by each integrated PMS.
...
Architecture & connection with other applications and services
...
Transform has its own database, UX, Admin site and API. The application uses chameleon WCF/internal API to obtain States and Countries. The chameleon OBE in its turn uses TransForm's API for posting deposit payments. TransForm works with 3 PMS types, hence, integrated with 4 PMS web services: LMS API, V1 API (developed by b4checkin), HMS Infor, Opera WS.
Transform also uses the following b4checkin services: b4email and b4payment. The integration with b4payment allows processing the transactions, the integration with b4email simplifies email sending.
...
- Guest inputs payment data
- The guest on the 1st page selects preferable payment types and fills in the form with data required for selected Type. e.g. for reservation the confirmation number is required, for group we need booking ID and group name
- On the 2nd page guest fills in credit card form
- The guest on the 1st page selects preferable payment types and fills in the form with data required for selected Type. e.g. for reservation the confirmation number is required, for group we need booking ID and group name
- The information filled in at 1a step is validated by requesting data from the PMS (V1, LMS or Opera)
- TransForm sends credit card and cardholder data to b4payment. b4payment in its turn calls the required payment gateway and processes the transaction. Transaction response is sent to b4easypost
- Storing the payment information
- Disregarding approved or not approved transaction result TransForm traces the info guest submitted
- Only if transaction is approved b4easypost stores payment info also.
- If selected payment type was configured to support /wiki/spaces/BTD/pages/124092464 transactions and guest selected to send Auth transaction at 1st step skip this step. b4easypost posts payment/deposit to PMS. The process could vary depending on PMS, but this only matters on lower level of detail. If payment posting to PMS failed - sent error email with payment details to property, so they can post it manually.
- Send email to guest (if configured) and to property with payment information. The email is sent via b4email.
Simplified Workflow
...
Attached Visio diagrams
EasyPost Architecture with Chameleon.vsdxEasyPost Architecture with Chameleon.vsdx
EasyPost Architecture (2022-01-20).vsdx
EasyPost Architecture (2022-03-25).vsdx
TransForm Workflow Summary - v1.0.vsdx
TransForm Workflow Summary.pdf