Paymetric connectors
Important
Optimizely Configured Commerce has an integration with Spreedly, a global payments ecosystem, to give you access to more payment gateway options. When implementing new payment gateways on your Configured Commerce storefront, you must select a payment gateway and a payment method Spreedly supports. The previous payment connectors are no longer supported.
Paymetric is a plug-in that you can configure to process payments when completing an order on your Configured Commerce website.
Paymetric does not use TokenEx like other Configured Commerce Payment Gateways, rather it uses Paymetric's own iframe. Because of this, card transactions requiring card entry through the administration console are unavailable when Paymetric is used as a payment gateway.
Note
Storefront saved card functionality was released in 5.0.5 for Paymetric.
Note
Paymetric is not currently available with the Optimizely Mobile application.
Settings (Iframe)
- Go to Admin Console > Administration > System > Settings.
- Search for and select Payment Gateway Iframe.
- Select Paymetric from the Payment Gateway IFrame menu.
- Populate the following fields with the criteria provided via your Paymetric account to configure Paymetric XiIntercept as the payment Iframe in Configured Commerce: These settings are currently restricted to Optimizely-only roles. If changes need to be made, submit a Support ticket. Due to data incompatibility across iframes, changing to a different iframe (such as TokenEx, Paymetric, Square Drop-in, or Adyen Drop-in) deletes all existing saved payment methods for all web users.
Field Name | Description |
|---|---|
Test Mode | If Yes, the system will use the test endpoint, otherwise it will use the live endpoint. Default value: On |
Merchant ID | Enter the Paymetric Merchant Id (This value is a GUID). |
Shared Secret Key | Enter the Paymetric Shared Key. |
CSS Location | Enter the absolute location of the CSS file for the you wish to render the Paymetric Iframe on. |
Security Code tokenization | Enables security code tokenization. Default value: Yes |
Iframe Template | Select the template for the Paymetric iFrame to render. For example, Creditcard asks only for the credit card number, while CreditcardCvv also prompts for the CVV. Default value: CreditcardWithCvv |
Payment Methods | Enter the payment methods you wish to be rendered in the Paymetric Iframe. Supported values (case sensitive): american express, discover, jcb, maestro, mastercard, visa, diners. |
Settings (payment gateway)
- Go to Admin Console > Administration > System > Settings.
- Search for and select Payment Gateway.
- Select Paymetric from the Payment Gateway menu.
- Populate the fields listed below with the criteria provided via your Paymetric account to configure Paymetric XiPay as the payment provider in Configured Commerce.
- Merchant ID – The Merchant ID for your Paymetric account.
- Username – The API Username for your Paymetric account.
- Password – The API Password for your Paymetric account.
- Test Mode – Turning this option on uses the Paymetric Test URL. Default value: On.
- Pre-Authorizations Only – When this setting is enabled, only pre-authorizations (card verification transactions) are submitted. This is used for workflows where the ERP makes both the authorization and the capture. Default value: Off.
- Use Ship To – Turning this option on uses the customer ship to address instead of bill to if selected during checkout. Default value: Off.
- Expiration Date Format – Select the format for expiration dates being sent to Paymetric XiPay. Default value: MM/YYYY.
- Transaction Type Message Type when Use Stored Card – This setting sends in a header-level value when customer is using a stored card for the TR_TRANSTYPE_MGGTYPE field in XiPay gateway. Default value: CUSE.
- Transaction Type Message Type when No Stored Card – This setting sends in a header-level value when a customer does not store a card for the TR_TRANSTYPE_MGGTYPE field in XiPay gateway. Default value: CGEN.
- Transaction Type Message Type when Submit Stored Card – This setting sends in a header-level value when customer is submitting a stored card for the TR_TRANSTYPE_MGGTYPE field in XiPay gateway. Default value: CSTO.
- Submit Two-Character Card Types – Turning this setting on uses two-character values (such as “vi” for “Visa”) when submitting card types to Paymetric XiPay. Default value: Off.
Note
Configured Commerce does not store sensitive credit card or profile information.
Note
CVVs are not stored in Configured Commerce, and as such, are not passed to the Paymetric XiPay gateway for authorizations or sale transactions.