Sign Up
  1. Znode
  2. Solution home
  3. System Configuration & Management - V10
  4. Managing Payment Methods

Payment Plugin Frequently Asked Questions

TABLE OF CONTENTS

What is Spreedly?

Spreedly is a payment aggregation platform providing access to a global payments ecosystem. Znode has partnered with Spreedly to offer an array of payment gateways and payment methods in the Znode 10 payment module. Spreedly acts as a single pipeline for Znode to submit payment requests to a multitude of gateways via multiple supported payment methods.  A high-level representation of the integration is depicted below.

To maintain PCI compliance, Znode leverages the Spreedly iFrame payment form to collect sensitive credit card information in the checkout workflow. Spreedly provides Znode a token value representing the credit card information. The token value is then used for transaction processing.  

Access to the Spreedly payment network is included in a Znode 10 installation.  Each customer will be allocated a production and non-production Spreedly environment to align with their Znode environment(s). In the Znode Spreedly payment plugin, a customer will select their desired payment gateway and provide their payment gateway credentials.

Which payment gateways and methods does Spreedly support?

The Znode 10 installation is preset with commonly requested payment gateways by default. The Znode 10 default installed gateways do not reflect Spreedly’s breadth of gateways. To use the Spreedly plugin, customers must select a payment gateway and a payment method that Spreedly supports.  

If the customer’s preferred payment gateway and/or payment method is supported by Spreedly but is not included in the Znode 10 installation, please reach out to your aligned Implementation Team or the Znode Support Team to request the payment gateway and/or payment method be added to Znode 10. Further details on this request process are included in the Frequently Asked Questions.

If Spreedly does not support a customer’s preferred payment gateway and/or payment method, a custom plugin may be developed for and installed into Znode 10 for payment processing. 

If assistance is needed determining whether a payment gateway or method is supported, please reach out to your aligned Implementation Team or the Znode Support Team.

What Spreedly operations does Znode 10 natively support?

Znode supports the Spreedly Purchase, Authorize, Capture, Refund, and Void API operations.

How does a Customer request a Spreedly supported payment gateway and/or payment method be added to Znode 10?

When requesting a Spreedly supported payment gateway and/or payment method be added to Znode 10, the following information should be provided:

  • What payment gateway is requested?
  • What payment methods are requested?
  • Does the customer have an existing relationship with the payment gateway?
  • Does the customer currently use the payment method(s)?
  • If the customer currently has an integration with the payment gateway, whether from an ERP or existing eCommerce platform, configuration information for that integration should be provided. Configuration information includes URLs for connection points and what credential fields are used. (Actual credential values are not needed to submit this request, just the names of the credential fields.) This information helps confirm which of a payment gateway’s integration methods should be connected to Znode. 
  • A brief description of the expected payment processing flow within Znode. For example, when requesting credit card processing, identify whether Znode will be verifying, authorizing, and/or capturing a sale.

Additionally, customers will be asked to furnish their own test credentials for the payment gateway. Those credentials are not required prior to submitting the request to add a gateway and/or method.

Once a request has been received by Znode, the steps to fulfill the request include:

  • Znode reviews the gateway’s alignment to Znode native workflows, i.e. verify, authorize, capture, etc.
  • Znode configures the gateway’s specific integration within Spreedly.   
  • Znode attempts to connect to the requested gateway via Spreedly.  
  • If connectivity exists, Znode validates all standard Spreedly transactions with the gateway to ensure expected behaviors.
  • After successful validation and if not already complete, the customer specific Spreedly environments are set up and the identifiers are provided to the requestor.  
  • The Znode 10 Product Team completes the configuration for the requested gateway and/or method to appear in Znode 10.
  • The configuration is deployed to the Znode 10 environment.
  • The customer configures their payment gateway credentials in Znode for the payment gateway and method, and proceeds with planned validation activities.

If the information in the request is incomplete, additional discovery and validation time is required to add the payment gateway/method to Znode 10.

In some cases, Znode will need to do some additional testing of the preferred gateway and/or payment method to ensure compatibility with a Znode implementation; or Znode may need to accommodate some additional settings in the Admin tool to support the preferred payment gateway and/or method. For these cases, additional time will be required to prepare Znode for a Customer’s testing of the payment gateway. 

If a requested gateway and/or payment method conflicts with the Znode implementation or cannot be implemented in a PCI-compliant way, Znode reserves the right to decline enabling the requested gateway and/or method. 

How does a Customer complete payment process testing and validation for the Spreedly plugin?

Customers should perform testing and validation of a Znode payment plugin implementation. It is recommended that a Customer verify, in the payment gateway’s system, any transactions completed via Znode.  

Customers will not have access to Spreedly to verify the passthrough of a transaction.  If a transaction fails to make it into Spreedly, the Znode system will handle the error and provide appropriate feedback to the user.  If a transaction successfully passes through Spreedly to the payment gateway but errors at the payment gateway, the payment gateway’s system should provide visibility to the cause of the failure. 

If after reviewing Znode’s and the payment gateway’s available information, there are still questions as to the cause of a transaction error, please submit a request to Znode for support.

Do Znode Customers need a business relationship with Spreedly?

Znode Customers do not need a relationship with Spreedly; the relationship with Spreedly is owned by Znode. Customers must continue to have direct relationships with the payment gateways they use for processing payments on Znode.  

Spreedly has provided Znode with a management portal for managing Znode’s business. Customers will not have access to this portal as it is targeted to the business relationship between Znode and Spreedly.

Is Spreedly PCI Certified?

Yes, the solution Znode has with Spreedly is PCI compliant.  Spreedly’s PCI compliance documents - including the attestation of PCI Compliance - is publicly available. For further information on Spreedly’s security capabilities and compliance, please visit Spreedly’s Trust Center. 

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.

Managing Payment Methods