PayPost-v5 Card Holder Account Transaction Processing

CityPay offer merchants the ability to create an account for each processing customer and store the card details for future use. Examples of usage are

  • repeat billing
  • account topups
  • faster checkout
  • simplification of processing
  • linkage of processing data

Accounts are able to be created using a merchant generated identifier linking processing data to your customer database.

Because data is stored in our PCI Level 1 accredited network, you are able to authorise transactions using a token based process without handling card data. This effectively removes your application from PCI PA-DSS requirements.

Accounts can be

  1. Automatically created when a new transaction is submitted for processing;
  2. Created and managed through an API (CHARMS); or
  3. Managed through the Merchant Control Panel.

Creating an Account Automatically on Transaction Processing

Note: This option must be enabled

To automatically create or update an account at the time of processing a transaction, the integration should provide extra parameters.

Parameter Name

Data Type

Requirement

Definition

accountNo

String

Required

The card holder account number that all transactions link to

firstname

String

Optional

The first name of the person the card holder account belongs to

lastname

String

Optional

The last name of the person the card holder account belongs to.

On receiving this instruction, if an account

  1. does not exist, an account is created. 
  2. already exists, the card data is updated with the provided information on the request. The new card data is subsequently set as the new default card for processing.

Sending a Processing Request against a Card Holder Account.

A standard API request should be constructed without card and address details. The addition of a single card holder account number is however mandatory to inform the API to process using that account.

Parameter Name

Data Type

Requirement

Definition

accountNo

String

Required

The card holder account number that all transactions link to

The transaction will process with the default card on record.

When using 3-D Secure for authenticating a card holder account payment, the API will require the account number parameter in the second request as well as the first.

 

Transactions will normally need to be coded as continuous auth processing compared to the default type for your merchant account. This may require a secondary account.

Evaluating the Response

A standard response mechanism is returned to your integration with an account action code if an account is updated or created. Dependent on the integration this may also include 3D-Secure.

Parameter Name

Data Type

Definition

Account

ecom:Account

The card holder account information for the response which contains attributes for reference, this is an XML value

Attribute Name

Data Type

Definition

accountNo

String

The card holder account number that the transaction was processed using

action

Integer

An action that has been performed against the account possible values are 

  • 0 No action performed
  • 1 Account Loaded
  • 2 Account Created
  • 3 Account Updated

Reporting of account data

The Merchant Control Panel will automatically link any transactions processed using the method to the card holder's account. This may be reported against by searching for the user account and viewing the recent history report for the user.

+44 (0)1534 884000