025643 Checkout.com Authorisation Flow Change
The Checkout.com integration within Khaos Control has been
modified such that it will be possible to instruct the system to take a full
value authorisation rather than zero value authorisation when saving a Sales
Order.
The Checkout.com integration within Khaos Control will be
modified such that it will be possible to instruct the system to take a full
value authorisation rather than zero value authorisation when saving a Sales
Order.
The payment process following these changes will be:
1. User creates a sales order as normal
2. Card payment type and CT account for Checkout.com is
selected as per existing process.
3. Card and cardholder details are entered into the existing
Num, Expiry, CSC, etc. fields as per existing process.
4. The Sales Order is saved and the card and cardholder
details are retained temporarily in memory (NOT stored in the database).
5. The system automatically attempts to authorise the
payment transaction using the card and cardholder details from memory. No SAD
nor unmasked PAN will be saved to the database at any time.
5a. If the
transaction is successful, token and/or transaction information will be stored
as at present.
5b. If the
transaction is flagged as fraudulent, the payment will be marked as HELD and
any reasons for the flag provided by Checkout.com will be available for review.
5c. If the
transaction is declined, the payment will be marked as rejected, as at present.
An update and changelog will be
applied as part of this development. Further configuration steps include:
3.1 System Data | Card Integration
Accounts.
With the new SVN option 'ENABLE_CARD_INT_MEMORY_STORE'
enabled a new ‘In Memory Store’ column is visible on this screen.
For this functionality to operate the
‘In Memory Store’ box should be ticked and the ‘Token Swap’ box unticked.