| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Overview
This endpoint serves as a Webhook target that OneInc calls after a customer submits or updates their payment method (bank account details) through OneInc's hosted form.
Trigger: OneInc sends an HTTP POST to this endpoint. Always. The trigger is never a user action in Origami or an internal Origami call. Origami only receives this webhook.
What happens before this endpoint is called:
- Earlier, through a separate process, Origami asked OneInc to collect a payment method from a customer
- OneInc emailed the customer a link to a hosted payment form
- The customer clicked the link and submitted their bank account details
- Now OneInc calls this endpoint to notify Origami that the customer has provided their payment method
What this endpoint does when called:
- Reads
ClientReferenceData1from the webhook payload to determine context and performs one of two actions:- Saves the payment token (from OneInc) to the customer's wallet in Origami
- If the context indicates a pending payout order: automatically initiates the bank credit
- Returns acknowledgment response to OneInc
How ClientReferenceData1 works:
When Origami originally asked OneInc to collect a payment method (step 1 above), it included a ClientReferenceData1 value in that request. OneInc stored it and now echoes it back in this webhook. The value isn't a routing choice — it's a record of why the payment method was requested in the first place. This endpoint reads it to know what context it's operating in:
ClientReferenceData1 value | What it means | What this endpoint does |
|---|---|---|
"ManualSavePaymentMethod" | An admin requested payment method collection with no associated order. | Saves token. Done. |
"OnlineOrderID:{id}" | A payout order triggered payment method collection because the customer had no saved token. | Saves token, then initiates bank credit for the referenced order. |
When to Use This Endpoint
This endpoint is a webhook target. You don't call it directly. You configure its URL in OneInc's dashboard so OneInc knows where to send notifications.
Prerequisites for this webhook to be called:
- OneInc integration configured in Origami (
OnlinePaymentProvider="OneInc") - Origami has already made a prior API call to OneInc requesting payment method collection
- OnlineCustomer record exists for the customer
- Customer has completed OneInc's hosted payment method form