credit_cardCapture Payment InformationVoicecredit_cardPaymentscapturePaymentInformation· Version 1.0.0

Hands the call to the PCI-isolated payment handler, which prompts the caller to key in their card number, expiry, and (optionally) CVV and billing ZIP, then charges the configured amount through the selected payment integration (Authorize.net or Meridian Payments). Meridian Payments sells only (authCapture) and needs the customer account number, the convenience fee, Capture CVV, and Capture Billing ZIP; without them the node routes on fallback before the caller is asked for a card. Card data never enters the workflow. Only the result, the card brand and last four digits, the transaction details and reason from the gateway, and, for tokenize, the stored profile ids are returned. Routes on default when approved, declined when the gateway declines, invalidInput when the caller fails to enter valid details, and fallback on a gateway or system error. A fallback with <prefix>_outcomeUnknown set to true means the card may have been charged anyway: do not retry the charge. If the call is being recorded, the recording is paused before the first card prompt and resumed when the capture ends, so that card entry is left out of the audio; a recording that starts during the capture starts paused. When the pause cannot be confirmed, Tandem tries to stop and delete the recording of the call, and the capture goes ahead. If neither the pause nor the delete can be confirmed, the capture still goes ahead and card entry may be in the recording.