Complete reference for all request parameters accepted by the PayFacto API v1.0. Parameters are grouped by functional category. Each endpoint requires a specific subset — refer to individual endpoint articles for the exact required and optional fields.
Version: v1.0 | Last updated: 2026-05-28
All parameters are passed inside a Base64-encoded payload form field. Assemble parameters as a cleartext query string (e.g. CompanyNumber=12345&MerchantNumber=53400000&...), Base64-encode the result, then POST as: auth-api-key={key}&payload={base64}.
Contents
These parameters appear on virtually every endpoint and establish the merchant identity and transaction context.
All monetary values are sent as integers in the smallest currency unit, zero-padded left to 11 digits. There is no decimal point — $4.29 is transmitted as 00000000429.
Card parameters for E-Commerce and MOTO transactions. For Semi-Integrated terminal transactions (InputType=N), send CardNumber as 40 spaces and ExpirationDate as 4 spaces — the terminal supplies all card data.
These parameters reference a previously processed transaction. Store these values from every transaction response — they are required for Void, Refund, and Completion operations.
Parameters specific to the Redirect (hosted payment page) session flow. The merchant creates a session server-side, then redirects the cardholder's browser to the PayFacto hosted page.
Authentication tokens generated by 3-D Secure verification (Verified by Visa and Mastercard SecureCode). These values are obtained from your 3-D Secure provider before calling the PayFacto API.
Parameters for mobile wallet transactions. The payment token is generated by the mobile device's authorized wallet and passed to PayFacto in place of card data.
Parameters used by the recurring billing module (/v1/recur/* endpoints) to manage subscribers, subscriptions, and invoices.
Additional parameters for specific use cases such as receipt customisation, credential-on-file transactions, and batch management.