Merchant Managed Card Tokens

This section deals with the message parameters that have to be included in a transaction request for Merchant Managed Card transactions.

The following parameters are stored during Merchant Managed Card transactions:

  • Token and Expiry Date stored by the Merchant for later processing (recommended)

note

The Billing and Shipping Address are stored locally or collected from the cardholder at time of transaction processing.

Store a Card on File

To store the customer card details, you need to process a CCVERIFY / CCSALE / CCAUTHONLY transaction. Every transaction authorized by Converge returns the following fields:

  • ssl_ps2000_data

  • ssl_approval_code

You must store ssl_ps2000_data and ssl_approval_code with the token and expiry date from this transaction to make future Card On File transactions.

note

If you already have a token with expiry date but do not have the ssl_ps2000_data or ssl_approval_code then you can store this data the next time you use the card for processing.

Recurring or Installment transaction using a Card on File

To perform Recurring or Installment transaction using the stored customer card details, submit CCSale request and include the following fields:

Recurring Billing

  • ssl_approval_code (from stored customer card details )
  • ssl_ps2000_data (from stored customer card details)
  • ssl_recurring_flag = 1

Installment Billing

  • ssl_approval_code (from stored customer card details)
  • ssl_ps2000_data (from stored customer card details)
  • ssl_recurring_flag = 2
  • ssl_payment_number
  • ssl_payment_count

One time Adhoc payment using a Card on File

To perform a one-time Adhoc payment using a stored customer card details, submit CCSale request for amount and include the following fields:

  • ssl_approval_code (from stored customer card details)
  • ssl_ps2000_data (from stored customer card details)
  • ssl_merchant_initiated_unscheduled = Y
  • ssl_entry_mode= 12