Paymonix
Paymonix
All articles

Email EventsUpdated 3 days ago

Paymonix Email Events

Paymonix triggers different email events based on order status changes, payment actions, and tracking updates. These events can be used in your ESP (e.g., Klaviyo) to send automated flows to customers.

You will need to set up each flow with the properties sent from Paymonix. Properties can be viewed when you preview & test a flow in Klaviyo.

Abandoned Cart

  • Trigger: Related to “new” Paymonix order statuses (customer landed on checkout but did not select a payment method).

  • Configuration: Abandoned cart email events will send based on your input in Store Settings.

  • Optional: Cancel on last point — At the final interval (e.g., 0.5 hours), if the order status is still “new,” Paymonix will automatically cancel the order.



Payment Instructions

payment_instructions_{payment_code}

  • Trigger: Related to “pending” Paymonix order statuses.

  • Behavior: When a customer selects a payment method at checkout, Paymonix automatically sends the first payment instruction email for that method.

  • Customization: Additional intervals can be set within each payment method setting. Abandoned points are set by the hour. If cancel on last point is enabled, Paymonix will update the pending order to canceled.



Instruction codes include:

  • payment_instructions_check

  • payment_instructions_mesh

  • payment_instructions_opennode

  • payment_instructions_paypal

  • payment_instructions_pbp

  • payment_instructions_zelle

  • payment_instructions_btcpay

Payment Failed

payment_failed

  • Trigger: Related to “failed” Paymonix order statuses.

  • Behavior: Customers receive the payment failed email event and can still attempt payment on the order.

payment_failed_repeat

  • Optional: Store Settings allow you to add additional failed email events.



Order Status Events

canceled

  • Trigger: Related to “canceled” Paymonix order statuses.

  • Behavior: Sent when an order is canceled either automatically (via settings such as cancel on last point) or manually by a user.

  • Note: Customers with canceled orders cannot make payment on the same order.

  • Trigger: When payment is successfully received.

  • Behavior: Order is updated to “paid” and the email event is sent.

  • Note: Orders under fraud review will not receive this event until payment is approved.

order_placed

  • Trigger: Fires when an order is placed, even if flagged for fraud review.

  • Best Practice: You can use this for order confirmation emails, or paid for payment confirmation. Choose one or the other to avoid confusion.

refunded

  • Trigger: Related to “refunded” Paymonix order statuses.

  • Behavior: Sent when a Paymonix user initiates a refund.

ACH Events

  • ach_verification_failed: Sent when ACH payment verification fails. The customer may retry.

  • ach_verification_failed_last: Sent when ACH verification fails a second time. The customer cannot retry, but may use another payment method.

Fraud Events

  • order_fraud: Related to “fraud_review” statuses. Triggered when an order is moved into fraud review by the Paymonix system.

Receipt Events

  • send_achpc_receipt: Manually triggered by a Paymonix user sending an ACH receipt from the order dashboard.

  • send_card_receipt: Manually triggered by a Paymonix user sending a card receipt from the order dashboard.

Subscription Events

Paymonix supports a range of subscription-related email events. These events help you notify customers about new subscriptions, renewals, cancellations, changes, and failed payments.

new_subscription

  • Trigger: When a customer successfully pays for their first subscription.

  • Attributes included:

    • Product(s)

    • Recurring Price (subscription_recurring_price)

    • Order Total

    • Subscription Interval (weekly, biweekly, monthly)

    • Next Charge/Order Date (subscription_next_charge_date)

    • Shipping Address (subscription_shipping_address)

    • Billing Address (subscription_billing_address)

    • Last 4 digits of card (subscription_last_4_CC)

    • Original Order Number, Subtotal, Grand Total, Discount, Shipping Cost

    • Subscription Number

    • (Eventually) link to manage subscription

  • Notes: Templates should include clear instructions for customer service support, including how to modify or cancel. Orders placed on weekends/holidays will ship the next business day. 

subscription_renewal

  • Trigger: 3 days before a subscription renews.

  • Attributes included:

    • Product(s)

    • Recurring Price

    • Order Total

    • Subscription Interval

    • Next Charge/Order Date

    • Shipping Address

    • Billing Address

    • Last 4 digits of card

    • (Eventually) link to manage subscription

  • Notes: Templates should include clear instructions for modifying or canceling subscriptions.

subscription_canceled (End of Term)

  • Trigger: When an order and its related subscription are canceled.

  • Attributes included:

    • Canceled Date

    • Product(s)

    • (Eventually) link to manage subscription

  • Notes: Templates should guide customers on modification or reactivation if needed.

subscription_changed

  • Trigger: When a Paymonix user (or eventually a customer) updates their subscription.

  • Attributes included:

    • Subscription Interval

    • Subscription Price

    • Product(s)

    • Next Charge/Order Date

    • Shipping Address

    • Billing Address

    • Last 4 digits of card

  • Notes: Templates should highlight which attributes were changed and include customer service instructions.

Failed Subscription Renewal Events

  • failed_subscription_renewal

    • Trigger: First failed renewal payment attempt.

    • Attributes included: Subscription details, last 4 digits of card.

    • Notes: Email should say Paymonix will retry in 24 hours, with instructions to update payment details.

  • failed_subscription_renewal_second

    • Trigger: Second failed renewal attempt.

    • Attributes included: Subscription details, last 4 digits of card.

    • Notes: Email should confirm another retry in 24 hours, with update instructions.

  • failed_subscription_renewal_final

    • Trigger: Third failed renewal attempt.

    • Attributes included: Subscription details, last payment date, last 4 digits of card.

    • Notes: Final notice. Subscription is canceled due to non-payment. Include reactivation steps (e.g., update card details).

Cron Job Logic

  • 3 days before renewal, subscription_renewal is triggered

  • If failed_subscription_renewal triggered: Retry payment in 24 hours.

  • If failed_subscription_renewal_second triggered: Retry payment in 24 hours.

  • If failed_subscription_renewal_final triggered: Cancel subscription/order.


Fulfillment & Tracking Events

Triggered when a fulfillment integration updates the order’s tracking number in Paymonix.

Paymonix Events

Sent from Paymonix once the fulfillment software (Linnworks or Shipstation) processes your customer order and adds tracking.

  • ss_tracking_number_added
  • tracking_number_added

AfterShip Connection Events

Sent from Paymonix after Aftership sends shipment status updates of your customer order.

  • tracking_update_acceptancescan

  • tracking_update_arrivalscan

  • tracking_update_attemptfail

  • tracking_update_availableforpickup

  • tracking_update_delayed (external factors)

  • tracking_update_delivered

  • tracking_update_departurescan

  • tracking_update_exception

  • tracking_update_failedattempt

  • tracking_update_incorrectaddress

  • tracking_update_inforeceived

  • tracking_update_intransit

  • tracking_update_outfordelivery

  • tracking_update_pickedupbycustomer

  • tracking_update_returningtosender


Example: Event Properties from Paymonix

When email events are triggered, Paymonix sends structured properties you can use in your flows. Below is a sample payload:

Amount: 17.05865  

Bill_address: Test Test, Ukraine Way, Boston, MA 02130, United States  

Billing_name: Test Test  

Country_code: US  

Created_at: 07/16/2024  

Currency: USD  

Grand_total_formatted: $17.06  

Order_id: 1893913  

Order_public_id: 000213518  

Order_status: done  

Order_url: https://test.testing.dev/pay/tssSoANptouPuPNhlRYUMkks1Kwfn0Ws  

Pay_url: https://crypto.paymonixtest.com/i/7tFfTU1JA2vhm  

Payment_code: worldnet  

Payment_type: cc  

Product_id: 6254  

Quantity: 1  

Subtotal_formatted: $4.99  

Total_shipping_formatted: $10.99  

Total_discounts_formatted: $0.00  

Customer_email: [email protected]  

Customer_name: Test Test  

Image_url: https://test.testing.com/test.jpg

Was this article helpful?
Yes
No
Powered by