Converge allows for the tokenization of cards through both their Commerce Web Services and Hosted Payment Pages APIs (Application Programming Interface); for example, for card-present and card-not-present transactions. For more information on how this works in CivicPlus Pay, see our Saved Payment Methods article.
Disclaimer
This article is provided for informational and educational purposes only. If you are having trouble following the steps in this guide, please reach out to Converge’s support team.
Article Navigation
Shared Token Vault
It is recommended that before you start collecting saved payment methods, you instruct Converge to set up a shared token vault across all of your terminals. This will allow a user to save a card through one terminal but use it at another. If you do not have this setting on, you will run into processing issues. If you only have one terminal, for example, if you only take e-commerce transactions, then setting this up in advance is not as important. However, if you were to add more terminals in the future, you would lose all the cards you had collected. This is because Converge does not have a way to move cards from a single terminal vault to a shared vault and keep the same token IDs (Identification Designation). Since the IDs change, the connection between Pay and Converge is severed.
Viewing Your Stored Payment Methods
Cards-on-File saved through CivicPlus Pay can be seen under Customers in Converge:
Customer Names
You may see numbers in place of customer names in the Customers section of Converge. This occurs when the cardholder's name cannot be read off the card. This is typical for contactless and manually entered transactions.
Troubleshooting
Card Brand Showing as Unknown
If all of your saved cards are showing as "Unknown" for the card type, it may be because Converge is not configured to send this information to CivicPlus Pay. To fix this, double-check that you have the Card Short Description set to "Forward on Approval" and "Forward on Decline."
- Log in to your Converge account
- Select Settings, then select Payment Fields:
- Click the Edit icon next to the Card Short Description field:
- Make sure that the Forward on Approval and Forward on Decline checkboxes are checked:
- If you have made any changes, click the Update link:
- Be sure to click the green Save button following the section:
Saving a Payment Method Outside a Transaction
When trying to save a payment method outside a transaction, you will want to be sure that you have two specific custom fields added to Converge, or the request to save the payment method will fail:
The two fields you will need are CP Form Type and CP Form ID:
- Log in to your Converge account
- Navigate to Settings, then select Payment Fields:
- In the order section, click the Add Payment Field button:
- Fill out the following fields for the CP Form Type field. Be sure to make them match exactly, spelling and case matter:
- Name: cp_form_type
- Display Name: CP Form Type
- Display Name French: CP Form Type
- Section: Order Section
- Field Type: Text
- Minimum Number Characters: 1
- Maximum Number Characters: 50
- Check the Forward on Approval, Forward on Decline, and Show on Export Script checkboxes:
- Click the Add button:
- Select the Add Payment Field button to add another field by repeating steps 2 through 5, this time for the CP Form ID field:
- Fill out the fields with the following information:
- Name: cp_form_id
- Display Name: CP Form ID
- Display Name French: CP Form ID
- Section: Order Section
- Field Type: Text
- Minimum Number Characters: 1
- Maximum Number Characters: 50
- Check the checkboxes for Forward on Approval, Forward on Decline, and Show on Export Script:
- Click the Add link:
- Click the Save button:
- You should now have a total of three custom fields:
- You are now ready to try saving a payment method again
Comments
Let us know what was helpful or not helpful about the article.0 comments
Please sign in to leave a comment.