ECP One-Time Transactions
Knowledge Center >
For Users > Vindicia Subscribe Portal User Guide > Payment Capture Flows > ECP One-Time Transactions
ECP One-Time Transactions
Vindicia Subscribe Portal User Guide
- Vindicia Subscribe Portal User Guide Overview
Chargeback Reason Codes
Status Definitions
Payment Capture Flows
Reports
Billing Notifications and Templates
Chargebacks
Transactions
Campaigns
Tokens
Credits
AutoBills
Rate Plans
Billing Plans
Products
Accounts
Vindicia Subscribe Dashboard
Using the Vindicia Subscribe Portal
Overview
Vindicia Subscribe for Salesforce
ECP One-Time Transactions
The following diagram describes the Payment Capture flow for one-time transactions when customers provide a Payment Method of Electronic Check Processing (ECP).
Payment Capture Flow: One-Time Transactions and Electronic Check Processing
For one-time transactions with ECP:
- A merchant sends a transaction to Vindicia Subscribe to perform an internal validity check to ensure Account and Payment Method information meets internal consistency check, and optionally calls the ChargeGuard Fraud Screen to determine chargeback probability.
- If the transaction passes the validity check (and is within fraud screen threshold if chargeback probability is calculated), then the transaction is either sent for processing, or the merchant application performs additional work before explicitly submitting the transaction for processing.
- If the transaction fails the validity test, a failure reason code is returned (and if chargeback probability is calculated, a fraud screen score is also returned).
- Vindicia Subscribe submits transaction to the payment processor and can perform either a Validate and Deposit or just a one-time Validate (and optional Verify that can be configured by the merchant since there are typically additional payment processor fees incurred for verification services) when more processing is required before an explicit Deposit (for example, to ensure that a tangible good is shipped before capturing the transaction).
- When the transaction is deposited, Vindicia Subscribe sends a One-Time Inbound or Outbound Success notification.
- The payment processor submits the transaction to the appropriate ACH or CPA network.
- Following network rules, the funds are deposited into the merchant's account, or the payment network notifies Vindicia Subscribe of any declines.
- If the deposit is not declined after the payment-processor specific number of banking days (currently six days), then the transaction is marked Captured.
- If the deposit is declined due to insufficient funds, the payment processor retries the deposit based on a merchant-defined number of days and Vindicia Subscribe then waits another deposit cycle (that is, six banking days).
- If the customer's transaction is declined, the transaction is marked as a Hard Fail and Vindicia Subscribe sends a Hard Fail notification.
- If a transaction is refunded, Vindicia Subscribe sends a Refund notification.
Vindicia Subscribe Features
Learn MoreFor Developers
Learn More
Back to Top