Added a complete CYBS gateway integration example to the Runner.js guide:
cardNumberFieldSelector and cvvFieldSelector to target custom card/CVV iframe containers<select> elements rather than Runner.js-rendered fieldsname, address2, region, country, phone, email.New reference guide added for understanding processor responses:
respproc, respcode, respstat, and resptext fields returned on charge responsesNew optional fields added to the HPP create endpoint:
min_amount: Minimum transaction amount. Only valid when lock_amount is false.max_amount: Maximum transaction amount. Only valid when lock_amount is false.New boarding webhook event added:
merchant.deleted: Triggered when a merchant record is deleted from a Partner. Includes merchant details such as merchant_id, dba_name, deleted_by, and timestamp. See the Boarding Webhooks guide for the full payload reference.New feature added for automated recurring payment processing:
New endpoint added for vault payment account creation:
Action Required: If you store customer payment information for recurring billing or future use, you must now include COF parameters in your charge requests.
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 permissionNew Feature: Real-time validation of bank account information during tokenization (iStream gateway).
risk_info object with validation resultsA (Accept), W (Warning), D (Decline)risk_info.decision before processing ACH transactionsNew API Endpoint: Edit existing hosted payment pages without recreating them.
/api/v1/hpp/{hpp_client_id}: Update HPP properties dynamicallycc_mid) cannot be changed after creationDocumentation Enhancement: Added full copy-paste examples for each gateway.
New comprehensive guide added covering:
vault_holder_id parameter for vault managementEnhanced ACH payments guide with new required fields for Fiserv ACH compatibility:
payment_description, ach_discretionary_data, entry_class, credit_or_debitevent_table_pk to merchant_id across all webhook examplesThe following webhook guides have been added to the Run Developer site:
The following endpoint has been added to the Boarding API reference:
GET /boarding/v1/merchants: Retrieve a list of merchants with optional filtering and pagination.Generate links on-the-go with our HPP API. Customize a payment page with transaction-specific parameters and share the link directly to your customer for payment.
POST /hpp endpoint.This is the first release of many for this API, and we will keep you updated as more functionality is added to this feature. An accompanying guide will be added to our docs site in the coming weeks.
Transaction Status ID Mapping
trans_status_id mapping has been added to our guides (See ID Mapping).Custom Fields
We have expanded the footprint of Runner.js documentation. Please note the updated URLs and updated locations of information below.
Tokenize page:
Runner JS page has been created.
Get Started guide have been moved to this page.The Runner.js Versions page has been created.
The following endpoint has been added to the API Reference:
POST /oauth/token:
Retrieve an access token for the Reporting or Boarding APIs. To toggle the URL between Boarding and Reporting API token requests, click the url on the API reference.Minor cleanup of documentation reference links.
The Run Developer Boarding API is now available in the Run Developer center! For additional information regarding the Boarding API and to request credentials, please reach out to your Integration Delivery Lead or send a note to integrations@runpayments.io.
The following guides have been added to the Run Developer site:
The following endpoints have been added to the Run Payments API Reference:
POST /boarding/v1/merchants: Create a merchant in Run Partner.GET /boarding/v1/merchant:id: Retrieve a single merchant’s details.Welcome to Run Developer! This site provides integration guides and API reference docs for the most recent releases of all our products. As new features are launched, additional release notes will be shared here.
The following guides have been added to the Run Developer site:
The following endpoints have been added to the Run Payments API Reference:
POST /api_keys/refresh: Refresh your API key for the Payments API.POST /charge: Charge a payment account.POST /capture: Capture an authorized payment.POST /void-or-refund: Refund-or-void an authorization or transaction.GET /surcharge: Check if a transaction will incur a surcharge fee.