Overview

Webhook endpoint that OneInc calls to report payment status changes for payout orders. This is the second webhook in the OneInc payout sequence — it arrives after OneIncAcknowledgePaymentMethod and reports whether the ACH transfer succeeded, failed, was voided, etc.

Trigger: OneInc sends an HTTP POST to this endpoint whenever a payment's status changes. Origami does not call this endpoint — it only receives it.

What happened before this endpoint is called:

1. Origami initiated a payout through OneInc (either directly via CreditBankAccount or indirectly after OneIncAcknowledgePaymentMethod saved a token and kicked off the payout)
2. OneInc began processing the ACH transfer
3. The payment's status changed (e.g., submitted to gateway, issued, completed, errored)
4. Now OneInc calls this endpoint to notify Origami of the new status

What this endpoint does when called:

1. Looks up the OnlineOrder by PM_CR_PaymentID (which is the OnlineOrderID)
2. Maps OneInc's PM_Status string to an internal Origami order status
3. If the status changed: creates a transaction record and updates the order
4. If the new status is Success: sets PaidAmount and PaidDate on the order
5. If the new status is Error: stores the error details on the order
6. Returns "Payment feedback acknowledged successfully"

Key difference from OneIncAcknowledgePaymentMethod: That webhook fires once — when a customer provides their bank details. This webhook can fire multiple times over the life of a payment as it moves through statuses (submitted → issued → success, or submitted → error, etc.).

When to Use This Endpoint

This endpoint is a webhook target. You don't call it — you configure its URL in OneInc's dashboard so OneInc knows where to send payment status updates.

Prerequisites for this webhook to be called:

• OneInc integration configured in Origami (OnlinePaymentProvider = "OneInc")
• A payout was initiated through OneInc (via CreditBankAccount API call)
• An OnlineOrder exists with a valid OnlineOrderID that was passed to OneInc