NCR Counterpoint to iPaaS.com Payment Method Mapping Documentation

This mapping collection brings the payment methods maintained in NCR Counterpoint into iPaaS.com. It carries the payment method's code, its readable description, and a classification of what kind of tender it represents — cash, check, credit card, gift card, store credit, and the rest of Counterpoint's tender set.

This family does not itself carry deletions. Where a separate Delete collection exists for this entity it handles removals from Counterpoint to iPaaS.com; otherwise a removal in Counterpoint is not propagated. See NCR Counterpoint Known Limitations.

Source: PAY_COD · Destination: Name

This is a required field — iPaaS.com rejects the payment method without it. The pay code as maintained in NCR Counterpoint, carried across unchanged and used as the payment method's name in iPaaS.com.

This is the short code subscribers or their MiSP see against the payment method in Counterpoint, not its readable label — the label travels on Description. Counterpoint always supplies it, because it is the payment method's key.

Source: DESCR · Destination: Description

This is an optional field. The payment method's readable description as maintained in NCR Counterpoint, carried across unchanged. It is the label subscribers recognize where Name carries only the code.

Source: Lookup Translation — **CP Payment Method PAY_TYP To iPaaS** · Destination: PaymentType

This is a required field — iPaaS.com rejects the payment method without it. Classifies what kind of tender the payment method represents, so that iPaaS.com and any downstream system can reason about the payment without understanding Counterpoint's own codes.

NCR Counterpoint records the kind of tender as a single-letter code on the payment method. This translation converts each of those letters into the wording iPaaS.com uses. Unlike the other mappings in this collection, the value is not read from a Counterpoint column directly — it is produced by matching the code against the rows below.

Two rows therefore produce Cash: the cash code itself and the stored value card code. That is intended, not a duplicate to be cleaned up. Subscribers who need stored value cards distinguished from cash downstream should change the V row's result rather than remove it, and should confirm the value they choose is one iPaaS.com accepts.

The rows cover every tender code Counterpoint documents for this field, so a payment method that matches none of them indicates a code added outside Counterpoint's standard set. Because PaymentType is required, such a payment method is rejected rather than transferred without a type. Subscribers or their MiSP who add custom tender codes must add a matching row here before the first transfer.

iPaaS.com constrains this field to a fixed set of payment types. Subscribers editing these rows should validate any changed result in a staging environment before relying on it in production, rather than assuming an arbitrary label is accepted.

Errors raised while transferring these records surface at Dashboard / Integration Monitoring / Error Logs. The specific messages, their causes and their resolutions are documented in NCR Counterpoint Error Messages. A record stopped by an error is not retried automatically; it must be resolved manually.