CenPOS

CenPOS credit card tokenization vaults card details via the CenPOS tokens API. The resulting token can be reused for future payments without transmitting raw card data, reducing PCI scope for the merchant.

Features

✅ Tokenization Credit Card payment methods can be converted to CenPOS 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

Obtain API credentials (username and password) and your merchant ID from CenPOS. Use the staging host (abistaging.cenpos.net) for testing and production host for live traffic.

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

Name	Type	Description
host	string	(required) The CenPOS API host. Use the staging host for testing. Examples: abistaging.cenpos.net, abi.cenpos.net.
merchantId	string	(required) CenPOS merchant identifier used in the tokens API path. Examples: 790010220.
basicAuth	object	(required) Username and password for Basic authentication. Examples: [object Object].

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": "creditcard",
  "provider": "cenpos",
  "config": {
    "host": "abi.cenpos.net",
    "merchantId": "790010220",
    "basicAuth": {
        "username": "integration",
        "password": "your_password_here"
    }
},
  
}

Data Mapping

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

Authvia customerRef maps to CenPOS CustomerCode
Authvia paymentMethod.email maps to CenPOS Email
Authvia paymentMethod.expirationMonth maps to CenPOS Expiration
Authvia paymentMethod.expirationYear maps to CenPOS Expiration
Authvia paymentMethod.cardNumber maps to CenPOS CardNumber
Authvia paymentMethod.nameOnCard maps to CenPOS NameOnCard
Authvia paymentMethod.streetAddress maps to CenPOS Address.StreetAddress
Authvia paymentMethod.city maps to CenPOS Address.City
Authvia paymentMethod.state maps to CenPOS Address.State
Authvia paymentMethod.zipCode maps to CenPOS Address.ZipCode
Authvia paymentMethod.country maps to CenPOS Address.Country.Name
Authvia paymentMethod.countryCode maps to CenPOS Address.Country.Code
Authvia body.tokenId maps to CenPOS token