Process: Capture payment

Flow

Legend

Capture payment

Objective

Capture payments for a shipped order.

Description

This process supports the asynchronous nature of payments by performing the capture of payment for an order in a background process. The input to the process is all orders that have been shipped and have not had payment captured. On completion of the process, payment artifacts will be appropriately updated to reflect the capture and the order will be updated to reflect that payment has been captured. Communication with back-end payment systems may occur in this process depending on the payment type and the payment integration used.

The definition of what happens during payment capture varies by payment type and by the implementation of that payment. Some examples are as follows:

A credit card using batch processing for deposits
in this case, no financial transaction takes place at the time of capture; but rather, the captured amount is placed in a batch that will be settled at a later time. The purpose of using batches is to reduce transaction fees.
A credit card not using batch processing
in this case, a settlement would occur as the result of the capture.
A check
the implementation supporting BankServ ACH protocol supplied with WebSphere Commerce Payments deposits the check at authorization time. Therefore, capture payment in this case is actually a no-op. Other implementations may deposit the check at this point.
Line of credit
the accounts receivable record would be added and the amount remaining on the line of credit would be updated accordingly.
Offline payment method
the capture would be recorded and potentially placed in batch for later settlement if batches are supported.

Features

Customization

Integration with back-end systems for:

-- External accounting

-- Payment

Support for extension points

Edition

Professional, Business Edition

Tasks

Task Description Role
Process requested deposit (external) Payment administrator
Update trading agreement amount

This command does the following:

  • The default implementation inserts a row into the TRDDEPAMT table for the order with the depositAmount in the default currency of the store if all order items specify the same Trading Agreement. However, if NOT all the order items have the same Trading Agreement, this command inserts multiple rows, one for each order item, with the deposit amount of each order item converted to the default currency of the Store.
  • The deposit amount of an order item is the sum of the

ORDERITEMS.TOTALPRODUCT + ORDERITEMS.TAXAMOUNT + ORDERITEMS.SHIPCHARGE + ORDERITEMS.SHIPTAXAMOUNT minus ORDERITEMS.TOTALADJUSTMENT.

System
Debit external account

This is an extension point for interfacing to an external accounting system.

System
Deposit payment

This task executes the business-policy command to perform the deposit.

System
Set release capture date

Update the release by indicating the payment-capture date.

System

Business artifacts

Feedback