Stripe: Create charge with an existing customer ID

Use this action to charge a card using either a token or Stripe Customer ID. This action can only create a charge for customers already added to the Stripe vault, with a payment method stored.

Use case

• Create a charge to a credit or a debit card through a charge object
• Retrieve and refund individual charges as well as list all charges
• Charges are identified by a unique random ID

How to configure this action

This action requires a preconfigured Stripe integration. For more information on integrating PagerDuty Workflow Automation with other systems, please refer to the Integrations section of our help documentation.

Fields for this action

• Integration

  • Select your team’s integration from the list

• Customer ID

  • The ID of an existing customer that will be charged. Either source or customer is required

• Currency amount

  • Value representing how much to charge the card

• Currency

  • Enter the 3-letter ISO code for currency
  • The following currencies are supported: AUD, CAD, EUR, GBP, CHF, HKD, MXN, NOK, NZD, USD

• Name

  • Name of the cardholder

• Shipping:

  • Address line 1
  • Address line 2
  • City
  • State
  • Zip
  • Country

• Capture

  • Select True or False from the drop down to choose whether to immediately capture the charge.
    • Select True to immediately capture the charge
    • Select False to issue an authorization (or pre-authorization) for the charge that will need to be captured later. Uncaptured charges expire in 7 days.

• Description

  • Create a description to display with the charge
  • Receipt emails will include the description of the charge(s)

• Receipt email

  • The email address to send this charge’s receipt to
  • The receipt will not be sent until the charge is paid

  • If this charge is for a customer, the email address specified here will override the customer’s email address

    💡   Tip: Receipts will not be sent during test mode

What will this output?

Output fields for this action

• ID

  • Unique identifier for the charge

• failure_code

  • Error code explaining reason for charge failure if available

• failure_message

  • Message to user further explaining reason for charge failure if available

• fraud_details

  • Hash with information on fraud assessments for the charge. Assessments reported by you have the key user_report and, if set, possible values of safe and fraudulent. Assessments from Stripe have the key stripe_report and, if set, the value fraudulent

• outcome

  • Details about whether or not the payment was accepted, and why

• receipt_number

  • This is the transaction number that appears on email receipts sent for this charge. This attribute will be null until a receipt has been sent

• statement_descriptor

  • Extra information about a charge. This will appear on your customer’s credit card statement

• status

  • The status of the payment is either succeeded, pending, or failed