Pacorda's role
Pacorda, Inc. operates the Pacorda enterprise payment-processing service and manages authorized payments across compliance controls, collection, supplier payment, settlement monitoring, reconciliation, and ERP confirmation. Pacorda is not a bank and does not hold customer funds. Banking, payment, foreign-exchange, and other regulated financial functions are provided through eligible financial institutions and service providers where applicable.
Pacorda remains the customer-facing operator and accountable service provider within the scope of its agreement.
Financial partners
Production services may involve banks, payment processors, payment networks, account-verification providers, foreign-exchange providers, compliance vendors, and other regulated or specialized partners. The provider available to a customer depends on eligibility, contracting, geography, currency, payment method, risk review, and technical implementation.
A reference to a bank or provider in a demonstration, architecture plan, sandbox, or implementation discussion does not announce a production partnership, endorsement, account approval, or service commitment unless confirmed in an executed agreement and provider documentation.
Account and balance disclosures
Pacorda processes payments from verified funding accounts to verified payment destinations. A balance, status, or ledger view in Pacorda is an operational record and is not itself a deposit-account statement.
Any deposit-insurance treatment depends on the actual account structure, eligible institution, ownership capacity, records, and applicable law. It must not be inferred solely from a Pacorda screen.
Registration and bank-connection boundary
Providing a bank name, account reference, account-ending digits, ownership document reference, or other onboarding information does not connect Pacorda to a bank account, authorize a payment, permit Pacorda to move funds, or establish a corporate banking relationship.
If an organization is approved to proceed, Pacorda will arrange a separate secure, authorized verification session with the organization’s designated representatives. Banking information, authority, ownership, eligible payment methods, limits, and required approvals must be validated before any production banking connection or funds-movement capability is established.
ABA routing numbers, Canadian institution and transit numbers, CLABE, IBAN, BIC/SWIFT, and local clearing codes identify payment routes or accounts; valid format does not prove ownership, authority, account status, or eligibility. Pacorda verifies those facts separately through approved providers or controlled documentary review.
Buyer funding authority and supplier payout designation are separate capabilities. Each must be verified, authorized, independently approved, and activated for its intended use.
A bank name or logo displayed during registration confirms only that Pacorda recognized the institution selected by the registrant. It does not confirm the account, ownership, approval, partnership, connectivity, or availability of services.
Payment authorization
A user may initiate or approve a payment only if authorized by the relevant enterprise and configured policies. The enterprise is responsible for its internal authority, approvers, limits, user access, invoice accuracy, and lawful instructions.
Material changes to amount, currency, beneficiary, funding account, destination, or invoice allocation may invalidate prior approval and require new authentication, screening, and authorization. Payment or bank-account instructions are not accepted through ordinary email.
Compliance review
Account and transaction activity may be screened for sanctions, ownership, identity, fraud, anti-money-laundering, jurisdiction, counterparty, velocity, and other risk indicators. A payment may be delayed, rejected, returned, blocked, suspended, or placed in manual review by Pacorda, the enterprise, or a financial provider.
A successful automated check is not a guarantee that a transaction is lawful, risk-free, accepted, or final. Financial providers and authorities may apply independent legal obligations and may request additional information.
Distinct transaction states
Authorization, provider acceptance, processing, bank settlement, reconciliation, and ERP confirmation are separate events. Provider acceptance does not necessarily mean funds have settled; settlement does not necessarily mean the customer’s ERP has been updated; and an ERP failure does not reverse a completed bank settlement.
Displayed timestamps, expected dates, FX quotes, and processing estimates may change because of cutoffs, holidays, provider availability, investigations, returns, correspondent banks, or network rules.
Returns, reversals, disputes, and errors
Payments may be returned, reversed, recalled, disputed, rejected, or adjusted according to the payment method, provider rules, enterprise agreement, and applicable law. Pacorda may preserve the original bank outcome separately from later operational or accounting events.
Enterprises must review payment details before authorization and report suspected errors promptly through authenticated support channels. Reporting does not guarantee recovery, cancellation, or reversal.
Foreign exchange and cross-border services
Foreign-exchange rates, fees, value dates, and cross-border availability are provided by or through eligible financial partners and may be time-limited. Demonstration quotes are synthetic and must not be relied on for a transaction.
Cross-border services may require additional information, screening, purpose-of-payment data, beneficiary details, tax information, correspondent-bank routing, and country-specific disclosures.
Fees and production terms
Fees, pricing, limits, service levels, allocation of loss, settlement mechanics, and provider responsibilities are defined only in executed production agreements and applicable provider terms. Website descriptions and demonstrations are not binding offers.
Contact
Questions about these disclosures may be sent to [email protected]. Do not send account numbers, credentials, authenticator codes, or payment instructions by ordinary email.
