{"title":"Payment origin codes","slug":"payment-origin-codes","url":"https://support.storeconnect.com/articles/payment-origin-codes","url_markdown":"https://support.storeconnect.com/articles/payment-origin-codes.md","subtitle":null,"summary":"StoreConnect sets a payment origin code on every Payment record in Salesforce to identify how and where the payment was created. Use these codes to build Flows and automations that behave differently depending on the payment source.","type":"Help_Documentation","video_url":"","keywords":"payment origin codes, origin, s_c__origin__c, payment source, subscription payment, SU01, SU02, WS01, WC01, POS payment, API payment, Salesforce flow, automation","last_modified":"2026-08-21T07:12:35+0000","body_markdown":"StoreConnect sets an **Origin** field (`s_c__origin__c`) on every Payment record in Salesforce. This field contains a short code that identifies how and where the payment was created — for example, whether it was taken automatically by a subscription renewal job, during web checkout, or via Salesforce Payments.\n\nThis field is particularly useful for building Salesforce Flows and automations that need to behave differently depending on the source of a payment. For instance, you can use it to detect whether a payment was created by StoreConnect's subscription processing job, and trigger downstream logic only when appropriate.\n\n### AD01 — additional payment\n\nSet when an additional payment is made against an existing order. This allows supplementary charges to be recorded after the initial transaction has been processed — for example, when a store administrator applies a top-up charge or covers a shortfall on an order.\n\n### AP01 — API call\n\nSet when a payment is created through StoreConnect's API. This covers programmatic payment creation by external systems or integrations connecting directly to the StoreConnect API.\n\n### AR01 — API refund\n\nSet when a refund is processed through StoreConnect's API. This covers programmatic refund creation by external systems or integrations connecting directly to the StoreConnect API.\n\n### MS01 — manual subscription payment\n\nSet when a manual payment is made directly against a subscription — for example, when a store administrator processes an early or out-of-cycle payment on behalf of a customer.\n\n### PO01 — POS payment\n\nSet when a payment is taken through StoreConnect's Point of Sale (POS) system. This applies to in-person transactions processed via the POS interface.\n\n### SF01 — Salesforce payment\n\nSet when a payment is taken using the Salesforce Payments feature — typically via the payment iframe that opens on an Order record inside Salesforce.\n\n### SU01 — automatic evergreen subscription payment\n\nThis code is set when StoreConnect's subscription job automatically processes a renewal charge for an evergreen subscription. It is the primary code to look for in Flows that should only fire when StoreConnect has initiated the payment — not when a customer or admin has manually done so.\n\n### SU02 — automatic fixed-term subscription payment\n\nSet when StoreConnect's subscription job automatically processes a renewal charge for a fixed-term subscription. Used in place of **SU01** to distinguish fixed-term subscription renewals from evergreen ones when building Flows and automations.\n\n### WC01 — website one-off payment\n\nApplied when a customer completes a website checkout for a one-time purchase. This covers standard storefront transactions where the customer's payment details are not saved for future use.\n\n### WS01 — website subscription purchase\n\nApplied when a customer completes a checkout on the website and a subscription product is part of their cart. This covers the initial subscription purchase through the storefront, where the customer's payment details are saved for future automated billing.\n\n## Related topics\n\n- [Payments](payments)\n- [Subscription processing, payments and renewals](subscription-processing-payments-and-renewals)\n- [Taking order payments from Salesforce](salesforce-payments)"}