Changelog

September 30, 2026

• Added information about ACH return code testing scenarios.

• Added information about accepting in-person payments through supported payment terminals.

• Added the terminal payment type.
• Added the /terminals and /terminals/cancel endpoints.
• Clarified the description and usage of tokenType.

• Added support for including metadata in Apple Pay and PayPal tokenization requests.
• Expanded the Mark Cryptogram description to provide additional guidance.
• Added information about using Bluefin for in-person payment tokenization.

September 16, 2026

• Changed psAchPaymentType and standardEntryCode from string to integer with an int32 format. Their enum values are now represented as integers.
• Renamed isFraud to fraud.
• Updated supported export formats by replacing JSON with XLSX.
• Corrected several examples so that their values match the documented data types, including amount, discount, account-number, expiration-date, service-code, and merchant-category-code examples.
• Removed internal x-rbac metadata from the Risk – Direct Merchants, Risk – Payments API, and Risk Event Logs tag definitions.
• Simplified the special-character validation pattern without changing the characters it permits.

• Updated the status and previousStatus descriptions to clarify that they represent the current and previous payment transaction statuses.
• Updated the status values to include REMITTED and RETURNED.
• Removed UNDER_REVIEW, DISPUTE_WON, and PENDING from the documented status values.
• Updated the previousStatus values to include RETURNED; the existing UNDER_REVIEW, DISPUTE_WON, and PENDING values remain supported for previous statuses.
• Clarified that amount is the payment transaction amount represented as a BigDecimal.

• Added endpoints to create, update, and delete tags associated with merchant configuration nodes.
• Added CRUD endpoints for managing Bluefin configurations. A Bluefin account ID must contain exactly 12 digits, and each configuration can contain only one merchant.
• Added an endpoint for retrieving additional payment type AVS code mappings. Results can be filtered by payment type and map raw AVS codes to standard NPS AVS codes.
• Added the BLUEFIN authority where required for Bluefin configuration and additional payment type operations.
• Updated endpoint headings throughout the Configuration Service to use concise, action-oriented Title Case.
• Clarified section, endpoint, and field descriptions, including Service Settings, Inheritance, SFTP, Payment Codes, Direct Entity, and ACH Return File documentation.
• Corrected formatting, spacing, duplicated text, and malformed escape characters in several endpoint descriptions.

September 2, 2026

• Updated the UI SDK reference for PayPal and Venmo. The accountHolder object returned by the payment-verification response is flattened in the onTokenizationComplete result into four fields: accountHolderName, accountHolderId, phoneNumber, and emailAddress.

• Added the Remittance and Settlement guide.
• Added the Receipt Service guide.

• Added paymentId, which identifies a payment throughout its lifecycle and can be submitted as transactionInformation.originalPaymentId for a subsequent transaction.
• Deprecated transactionInformation.originalPaymentTransactionId in favor of transactionInformation.originalPaymentId. The deprecated field remains supported, and existing integrations do not need to change.

August 5, 2026

Updated the Apple Pay SDK documentation and examples to reflect the current integration flow. Session tokens are now applied using updateSessionToken(), and Apple Pay is rendered through the standard mount() method with paymentMethod: 'applePay'.

The update also corrects supported configuration options, result fields, cancellation handling, and error-code guidance. Recurring-payment examples now include only fields supported by NPS and clarify that NPS manages recurring payment plans, merchant validation, Apple Pay sessions, and payment-token processing.