Overview
Matrix sends credit card authorization forms through Sertifi. Before anyone can send one, an admin connects the property to your Sertifi account. This is a one-time setup per property, and a portfolio with several hotels does it at each one.
You go back and forth between the two systems, in this order:
- In Sertifi: get your API key
- In Matrix: paste the key and your portal address into the property, save and test the connection. Matrix then gives you a Target URL and a Web Push token
- In Sertifi: turn on Real Time Updates with that URL and token, so Sertifi tells Matrix what the guest did
You need admin access to your Sertifi account for the first half, and property setup access in Matrix for the second.
To send a form once this is done, see CC Authorization Forms: Collect a Card Through Sertifi.
Part 1: In Sertifi
Get to Sertifi the way you normally do
Open your Sertifi portal however your hotel normally reaches it. If you get to Sertifi for a Marriott property through Marriott's portal, use that same route. The steps below start once you are signed in.
Get the API key
- Open your Sertifi portal in a browser
- Click Administration. If a submenu opens, click Administration again inside it
- Click Account Settings
- The API key is at the top of the page
Keep it somewhere safe for Part 2. Treat it like a password.
Part 2: In Matrix
-
Open the property you want to connect and go to its Integrations tab
-
Find Sertifi under the Credit Card Authorization heading
-
In API Key, paste the key you copied from Sertifi
-
In Portal URL, enter your own portal address, the one this hotel signs in to. The easiest way to get it right is to copy it from your browser's address bar while you are signed in to Sertifi. It follows the pattern
https://www.sertifi.com/YourPortalName, where the last part is your portal's own name. A real one often reads as the hotel name and its property code run together, with no spacesDo not paste the example.
YourPortalNameis a placeholder and will fail the test. Another hotel's portal address connects this property to the wrong Sertifi account, so use the address for the property you are setting up. -
Click Test Connection. Matrix checks the key against Sertifi and, if it passes, saves the credentials and activates the integration in one step. A green indicator confirms it
Matrix encrypts the credentials before storing them.
Copy the Target URL and Web Push token
Below the buttons, the card has a Web Service Push section. Its Target URL is already filled in for you. The Web Push token is created when you save the integration; until then the card reads "Save the integration to generate its Web Push token."
Each integration gets its own token, and Matrix keeps it hidden until you click to show it. Copy both values for Part 3, and treat the token like a password.
Repeat Part 2 for each property that sends authorization forms. Each one has its own token.
Once the test passes, the property can send forms. CC Authorization Forms: Collect a Card Through Sertifi walks through sending one, with a screenshot of each stage from the send to the card being authorized.
Part 3: In Sertifi, Turn On Real Time Updates
Real Time Updates is how Sertifi tells Matrix that a guest opened, signed, or paid. You need the Target URL and the Web Push token from the end of Part 2.
If you skip this, statuses lag. A request you send from Matrix stays at Sent no matter what the guest does. Matrix polls Sertifi every 15 minutes as a fallback, so nothing is lost, but the status on the opportunity is behind.
- Open your Sertifi portal in a browser
- Click Administration. If a submenu opens, click Administration again inside it
- Click Account Settings
- Click Real Time Updates
- Click Web Service Push
- In Target URL, paste the Target URL from the property's Sertifi card in Matrix. It is
https://whgw.m1intel.com/cc-auth/sertifi - In Web Service Security Token, paste the Web Push token from the same card
- Make sure Use JSON Web Service Push is checked
- For each event in the table below, tick Subscribe, then click Select Fields and tick the fields listed for that event
Every event needs FileId. That is how Matrix matches an update to the right request. An event without it is discarded.
| Event | Fields to select |
|---|---|
| UserInvited | FileId |
| UserVisited | FileId |
| AgreementSigned | FileId |
| AgreementCompleted | FileId |
| AgreementExpired | FileId |
| FileExpired | FileId |
| SignerDeclined | FileId, DeclineComments |
| PaymentFailed | FileId, ErrorMessage |
| PaymentReceived | FileId, Status, ErrorMessage, CardLast4, CardType, AVSStatus, CVVStatus, FraudScore, FraudTriggeredRules, GatewayTokenId, GatewayTransactionId |
If the Test Fails
The message tells you why.
| Message | What it means |
|---|---|
| Invalid credentials | The API key is wrong. Copy it again from Sertifi's Account Settings page |
| A URL error | The Portal URL is not a full https:// address. Fix it and test again |
Fix the field it names and click Test Connection again.
FAQ
Does each property need its own Sertifi account? Each property connects its own Sertifi credentials. A portfolio sets this up at every hotel that sends authorization forms.
A form I sent is still showing as Sent. Why? Most often, Real Time Updates is not configured in Sertifi, or it has the wrong token. See Part 3. Matrix polls Sertifi every 15 minutes regardless, so the status catches up on its own, it just lags.
Do card details pass through Matrix? No. The guest completes and signs the form on Sertifi's secure page. See CC Authorization Forms: Collect a Card Through Sertifi.
Questions? Email support@m1intel.com