AutoPayment Feedback from One Inc

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

Overview

Webhook endpoint that OneInc calls when a customer enrolls in, or cancels, autopay (recurring payment) for a policy or billing account. This endpoint updates the IsRecurringPayment flag on the corresponding Policy or BillingAccount record in Origami.

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

What this endpoint does when called:

  1. Reads ClientReferenceData1 (PolicyID) and ClientReferenceData2 (BillingAccountID) from the webhook payload
  2. Reads InstallmentPlanStatus to determine whether autopay is being activated or deactivated
  3. Updates IsRecurringPayment on the appropriate record:
    • If PolicyID is nonzero: updates the Policy
    • If PolicyID is zero: updates the BillingAccount using the BillingAccountID
  4. Returns acknowledgment string to OneInc

How it determines which record to update:

ClientReferenceData1 (PolicyID)ClientReferenceData2 (BillingAccountID)Record updated
Nonzero (e.g., "42")IgnoredPolicy with that ID
"0"Valid ID (e.g., "15")BillingAccount with that ID

How it determines the new value:

IsRecurringPayment is set to true if InstallmentPlanStatus == "Active", false otherwise.

Separate flow from payout webhooks: This endpoint is not part of the payout sequence (OneIncAcknowledgePaymentMethodOneIncPaymentFeedback). It handles a completely independent concern — recurring payment enrollment.

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 autopay enrollment notifications.

Prerequisites for this webhook to be called:

  • OneInc integration configured in Origami (OnlinePaymentProvider = "OneInc")
  • Customer has enrolled in or canceled autopay through OneInc's interface
  • The autopay plan was set up with ClientReferenceData1 = PolicyID and ClientReferenceData2 = BillingAccountID

Body Params
json
required
Defaults to { "Id": "string", "SessionId": "string", "Type": "string", "Timestamp": "2025-12-14T01:27:11.530Z", "Data": { "PM_CR_PaymentID": "string", "PM_IP_PaymentID": "string", "PM_Amount": 0, "PM_Funded": true, "PM_Status": "string", "PM_PaidDate": "string", "PM_ClearedDate": "string", "PM_EscheatDate": "string", "PM_CheckNumber": "string", "PM_CheckPrintDate": "string", "PM_MailTrackingNumber": "string", "PM_MethodID": "string", "PM_Monitored": "string", "PM_RejectPayeeId": "string", "PM_RejectReason": "string", "PM_New_Method": "string", "PM_Orig_Method": "string", "PM_Selection": "string", "PM_Method_Last4Digit": "string", "PM_ReIssue": "string", "PM_ErrorCode": "string", "PM_ErrorMessage": "string", "PM_CarrierId": "string", "PM_ENV": "string" } }

This request body is constructed and sent by OneInc. You receive and process it. You don't build it.

The payload structure is defined by OneInc. The example provided here is for reference only.

Responses
200

Language
Credentials
Header
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json