Postman collection
Payments Write

pixiSetCreditCardInfo

Masks the stored credit card number and CVC of an order's address and/or stores a payment authorization code on the order.

Updates credit card related data for the order identified by OrderNr. Two independent steps run, depending on the parameters:

  1. Scrambling (if ScrambleData = 1, the default): the address referenced by the order (OrderHeader.AddrRef) is looked up. If its card number ACardNr does not already contain ****, it is replaced by ************* followed by the last four characters of the original number, and the card verification code CCCVC is set to ***.
  2. Authorization code (if AuthCode is not NULL): the value is written to OrderHeader.ccpPayID of the order.

Both steps can be combined in one call. The procedure returns no result set. It only sets a return code: 0 if at least one row was updated, otherwise 1.

Notes

  • The return code (0/1) is a T-SQL RETURN value and is not delivered as a row; SOAP clients usually cannot see it. There is no explicit error for an unknown OrderNr – nothing is updated in that case.
  • The masking affects the address record itself. If the same address is referenced by other orders or the customer, the card data is masked for all of them.
  • Addresses whose ACardNr is NULL are not masked (the NOT LIKE check is not true for NULL). Already masked numbers (containing ****) are skipped, so repeated calls are safe.
  • The order lookup uses NOLOCK; updates use ROWLOCK. No explicit transaction is used, so the two steps are not atomic.
  • To only store an authorization code without masking, pass ScrambleData = 0.
  • The helper util.TempTableDrop is called to drop the temporary table; its definition is not attached.

Tables used

OrderHeader · Write Addresses · Write
SQL object:
dbo.pipiSetCreditCardInfo
Updated at 2026-10-30