Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

While we want Stripe to do the heavy lifting of the payment processing, you want to know what has happened, and have it recorded in your Salesforce org, so that you can maintain it as your single source of truth. To do this, you will utilise webhooks from Stripe. Every time an event occurs in Stripe, if you have set up the webhooks correctly, you will receive all the necessary data into Salesforce, ready for PosiPay to update your records.

...

You must select which events to listen to for each Stripe object. There are 3 objects that PosiPay needs to listen to. Each object has different events, so carefully select only what is needed. Wherever possible, do not select all events available.

  1. Charge

    • charge.failed 

    • charge.pending 

    • charge.refunded 

    • charge.succeeded 

    • charge.updated 

      image-20240904-073805.pngImage Modified

  2. Invoice
    Please note: If the PosiPay version is 92 and above please do not include the invoice.created and invoice.updated event.

...

  1. Payouts

...

  1. Payment

  • payment_intent.canceled

...

  • payment_method.attached

    image-20241206-021022.pngImage Removed
  • payment_method.automatically_updated

    image-20241206-021233.pngImage Removed

  • payment_method.updated

    image-20241206-021321.pngImage Removed

  1. Customer

...

customer.created

...

customer.updated

...

    • invoice.created

    • invoice.payment_failed 

    • invoice.payment_succeeded 

    • invoice.updated

    • invoice.marked_uncollectible 

...

  1. Payouts

    • payout.failed 

    • payout.paid 

...

  1. Payment

    • payment_intent.canceled 

...

Next place to go: Step 5 - Schedule an Invoice

...