Fiserv Paypoint

Fiserv Paypoint Gateway facilitates secure online payment processing for a diverse range of e-commerce systems.

Features

✅ Tokenization ACH payment methods can be converted to Fiserv Paypoint payment tokens. ✅ Auto Tokenize Can use features.auto-tokenize to have all corresponding tender types auto converted to tokens. See tokenize for more details.

Resources

Configuration

For ACH transactions through Fiserv Paypoint, ensure the Application Id and Merchant Id with your Fiserv representative.

This table describes the required or possible attributes needed to configure a merchant product for this type.

Name	Type	Description	Rules
applicationID
type
description
examples
label

Features

All tokenize products support the following features attributes.

Name	Values	Description
auto-tokenize	true or false (default)	Can be provided for one tokenized product per payment method type (tender type). When set, any call to create a payment method for that underlying tender will automatically be converted to a token of the defined type.
auto-permission	single-use or use (default)	Used to determine the permission to automatically set on each token created using this tokenization provider. Setting a value of single-use will mean a token is deleted on each successful use.

Enabling this Product

Using create-merchant-product API you can add a new product to your merchant record. Below is an example configuration for the payload of that request.

{
  "line": "tokenize",
  "product": "ach",
  "provider": "paypoint",
  "config": {}
}

Data Mapping

The following bullet points outline the mapping of data fields between the Authvia platform and the Fiserv Paypoint system, detailing the correspondence of specific attributes for seamless data integration.

Authvia transaction.id maps to Fiserv Paypoint interactionID
Authvia transaction.references.customer maps to Fiserv Paypoint payeeID