On this page:
Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Overview
The settings for Corporate Payment Cards allow a company you to write set a policy around a specific set of credit card cards that share a common Bank Identification Number (BIN). The BIN is the first six to eight digits of the card number. You can require users in one or more groups to book travel using a credit card from that defined set of cards sharing a BIN number.
Benefits
...
Requires users to give a reason why they are not using their assigned corporate card stored within their profile.
Corporate Payment cards can be configured based on group(s).
Need to Know
Difference between the Site Payment Card and Corporate Payment Card
Site Payment Card: Company corporate card(s) configured at the site level, which the traveler has the option or is required to use.
Corporate Payment Card: Individual corporate cards stored at a user profile level, for which a policy has been written around the use of the BIN number.
Note: For the configuration to work you will need to update the configurations under both Corporate Payment Cards and Travel Policy.
...
and Need to Know
Creating a corporate payment card set allows you to specify a group of related company credit cards, based on their shared BIN, that are considered in-policy for booking travel for specific user groups.
Corporate payment cards are similar to but used differently than Site Payment Cards:
Corporate payment card: A corporate card with its card number stored at the traveler user profile level. As detailed below, at the site level, you create a card set based on a shared BIN number, and then assign that card set to one or more user group/s. If users in that group do not select a corporate payment card to use for travel, the trip is considered out-of-policy, and the user will be required to select from a list of compliance codes.
Site Payment Card: A corporate card with its card number stored at the company site level. Site Payment Cards details how to create a site payment card, assign it to a site payment card set, and assign that set to one or more user group/s. Users in that group can be restricted to using only the site payment card for travel, or they can be allowed to use either the site payment card or a card stored in their profile.
Tip: To see examples of the traveler experience on the purchase page for corporate payment cards, see the examples in Payment Options.
The client must provide you with the financial institution’sBIN number, which is typically
...
the first six to
...
eight digits of the card number.
...
...
Create Corporate Payment Card
...
Set for BIN
Start by creating a new corporate payment card set:
From the Partner Dashboard home page, select click the Settings in the Edit Site column for the site that needs updating.From the Services tab, select link to the right of the site you want to update.
Click the Services tab.
Under the Travel heading, click Corporate Payment Cards.
SelectClick Add a new payment card set.
Complete Name the set in the Corporate Payment Card Set fields as outlined belowName field.
Corporate Payment Card Set Name: Enter a name for the set (e.g. Corporate Payment)In the Payment Card Restrictions section, enter details around the BIN as follows.
Card Name: Enter name to define
this set of credit cards that share the BIN.
Card Type: Select the credit card type.
Card Number: Enter BIN number provided by client
Select Save.
Travel Policy
- From the Services tab
. It should be the first six to eight digits of the credit card number.
If you want to add another BIN to share the same policy you’ll create next, click the Add Payment Card Restriction link and add another card and BIN.
Click the Save button at the bottom of the page.
Configure Travel Policy for the Corporate Payment Card
Next, add the corporate payment card set you just created to a travel policy:
Click the Services tab.
Under the Travel heading, select Travel Policy.
Select Policy List.
Select policy to be updated
Take one of the following steps as appropriate:
To create a new travel policy, click the Add A New Travel Policy link. If you want to add other restrictions to this policy, see Travel Policies for details on setting other restrictions.
To update an existing policy, click the name of the policy to update.
Scroll down to Flight Payment Card Options and select the appropriate card from list.
Select Save.
Compliance Codes
If you have a policy set, be sure to update compliance codes. You may not have relevant codes which would apply to the customer.
See Compliance Codes for further information around setting up compliance codes.
Service Rules and Commit Changes
Assign the Corporate Payment Card to the appropriate Service Rules.
On the Partner Dashboard, select the link to the left of the Deem logo indicating that changes are not applied.
Select Commit to apply the changesClick the Save button at the bottom of the page.
Page Properties | ||||||
---|---|---|---|---|---|---|
| ||||||
|
Add Corporate Payment Card Set to Service Rules for a User Group
The last step is to assign a corporate payment card set to the service rules for a specific group, as follows:
At the top of the partner dashboard, click the Rules tab.
Click the Service Rules link.
On the Service Rules page, next the name of the group to which you want to assign the corporate payment card set, click the Edit or Add link as applicable.
Scroll to the Corporate Payment Card Restrictions section. From the Payment Card Set dropdown, select the corporate payment card set to assign to this user group.
If you have not also applied your Compliance Codes, also select the appropriate compliance codes in the Compliance Codes section on this page.
At the bottom of the page, click the Save button.
Repeat the above steps if you want to apply the same or other card sets to other groups.
After making all updates, click Save Priority Changes at the bottom of the page.
Commit all changes (click the # changes not applied link at the top-right and click Commit).
Test the site to ensure the corporate payment cards are working correctly for each user group.