Card On File (COF) - Required for Stored Credentials
Action Required: If you store customer payment information for recurring billing or future use, you must now include COF parameters in your charge requests.
- Card On File Guide
- New Required Parameters:cl
cof: Set to "C" (customer present) or "M" (merchant-initiated)cof_sched: Set to "Y" (scheduled recurring) or "N" (one-time/unscheduled)cof_perm: Optional, set to "Y" if customer gave explicit permission
- When to Use: Any transaction using saved payment methods, subscriptions, or recurring billing
- Non-compliance Risk: Transaction declines and potential penalties
ACH Account Validation
New Feature: Real-time validation of bank account information during tokenization (iStream gateway).
- ACH Validation Guide
- What’s New: Runner.js tokenization responses now include
risk_info object with validation results
- Decision Codes:
A (Accept), W (Warning), D (Decline)
- Action: Check
risk_info.decision before processing ACH transactions
Hosted Payment Pages - Edit Endpoint
New API Endpoint: Edit existing hosted payment pages without recreating them.
- PUT
/api/v1/hpp/{hpp_client_id}: Update HPP properties dynamically
- Use Cases: Modify amounts, lock settings, customer information, or optional fields
- Note: Merchant ID (
cc_mid) cannot be changed after creation
Runner.js - Complete Integration Examples
Documentation Enhancement: Added full copy-paste examples for each gateway.
- New Gateway Examples:
- Cardpointe: Complete implementation with charge processing
- Cybersource: Custom field selectors and styling
- Payroc: Full validation and error handling
- ACH (iStream/Fiserv): Bank account tokenization with validation
- What’s Included: HTML forms, initialization code, tokenization workflow, and backend integration
API Updates
- order_id Parameter: Now auto-generated if not provided (previously required)
- Swagger Spec: Improved formatting and consistency across all endpoints
