Payfy

Payfy: Overview For Merchants

Payfy is a Georgia-based payment service provider that enables businesses to accept online card payments and selected alternative methods through a single integration. Payfy confirms authorization by the National Bank of Georgia under the Rules for Registration and Regulation of Payment Service Providers and provides API documentation for card and APM processing.

What Is Payfy

Payfy is positioned as a PSP that connects merchants to card acquiring and a set of alternative payment methods through a unified API. According to the site, Payfy supports Visa and Mastercard card transactions and offers features such as recurring billing, split payments, and risk management. The company states it is authorized by the National Bank of Georgia and provides a merchant-facing dashboard and API endpoints for live and sandbox environments.

Who Payfy Is For

• Online shops seeking a straightforward card acceptance setup with a hosted payment page option.

• Crypto platforms that need card rails and additional payment options aligned with the provider’s risk policies.

• Merchants selling cross-border into or from Georgia that require EUR, USD, or GEL processing.

• Teams that prefer API control plus ready-made flows for redirects, recurring billing, and webhooks.

If your product falls into very high-risk categories or originates from jurisdictions labeled high-risk by the National Bank of Georgia, Payfy indicates such traffic will not be accepted.

Supported Payment Methods And Brands

Cards

• Visa

• Mastercard

Alternative Payment Methods exposed via the API
The API specification includes an enum of supported method identifiers. Examples listed include:

• BASIC_CARD

• FLEXEPIN

• MACROPAY

• SKRILL

• PAYRETAILERS

• LOCALPAYMENT

• MONNET

• PAYPAL

• NETELLER

• TRUSTPAYMENTS

• PAYMAXIS

• GATE8TRANSACT

• TINK

• B2BINPAY

• CLICK

• MONETIX

• PERFECTMONEY

• VOLT

Merchants should confirm on boarding which of these methods will be available for their MCC, region, and risk profile.

Currencies And Regions

• Processing currencies: EUR, USD, GEL.

• Country acceptance: Payfy notes it does not accept card payments from high-risk jurisdictions as defined by the National Bank of Georgia.

• Use cases: Online shops and crypto platforms are mentioned explicitly as supported business types.

Settlement currencies and timetables are not stated publicly, so confirm settlement configuration during onboarding.

Key Features

• Recurring billing: Initiate a recurring chain using a token returned by the initial transaction. The API provides startRecurring and recurringToken fields to manage subsequent charges.

• Split payments: A feature described on the site for customers to complete a purchase using multiple cards.

• Risk management: Payfy indicates tools and policies that help merchants manage exposure and comply with local restrictions, including blocking high-risk jurisdictions per NBG lists.

• Hosted and direct capture options: If you are not PCI DSS certified to collect card data, the flow can redirect to Payfy’s page to gather sensitive data. If you are certified, the API allows sending card fields from your environment.

• Webhooks and redirects: The API provides webhookUrl for asynchronous status notifications and returnUrl or redirectUrl parameters to control the customer journey after authorization.

• Merchant dashboard: Payfy states you can review transaction history from the account interface.

• Support: Email support is available, with responses during working hours and an email channel for issues outside those hours.

Integration And API

Authentication

• Bearer token using a Shop API Key in the Authorization header.

Core endpoints

• Create payment: POST /api/v1/payments

• Find payment: GET /api/v1/payments/{id}

• List payments: GET /api/v1/payments

Environments

• Production base URL: https://app.payfy.me/api/v1/

• Sandbox base URL: https://app-demo.payfy.me/api/v1/

Data model highlights

• Amounts and currency: Request in currency with ISO 4217 or a crypto symbol. If the provider-side currency differs from the customer-facing currency, customerAmount and customerCurrency can reflect the original request currency and amount.

• Customer and address: Objects are provided for KYC-relevant details where required.

• Payment method: The paymentMethod field uses the enum values listed above.

• Recurring: Use startRecurring: true to begin a chain, then store and send recurringToken for future debits.

• Webhooks: Supply webhookUrl to receive status notifications.

• States and error handling: Responses include statuses such as PENDING plus an errorCode. The docs enumerate provider, issuer, 3DS, anti-fraud, and validation error categories to support deterministic handling.

Sandbox testing

• Successful deposit tests require amounts under the stated sandbox threshold and provide test cards covering 3D Secure enrolled and non-enrolled paths. This allows merchants to validate both approvals and declines before going live.

Security, PCI DSS, And Compliance

• PCI DSS: Payfy’s documentation states that merchants must be PCI DSS compliant to submit card data directly in API requests. Merchants without appropriate certification should avoid sending card fields and instead use the provider’s hosted collection page.

• 3-D Secure: Sandbox test numbers cover both enrolled and not-enrolled cases, which is useful when validating your 3DS challenge and frictionless logic.

• Jurisdictional controls: Card payments from high-risk jurisdictions as defined by the NBG are not accepted.

• Data access: The FAQ states merchant personal information is accessible to Payfy and the acquiring bank, aligning with typical PSP processing roles.

If you are unsure about your PCI scope, review the PCI SSC merchant resources and select the appropriate SAQ type before deciding between hosted and direct flows.

Conclusion

Payfy provides a regulated PSP option for card and selected APM acceptance, with clear API primitives for payments, recurring billing, redirects, and webhooks. The site describes Visa and Mastercard support, EUR/USD/GEL processing, and policies aligned with National Bank of Georgia rules. Pricing is bespoke, and merchants should confirm production availability of specific APMs, settlement terms, and reporting before go-live. For teams comfortable with API integrations that want a hosted fallback for PCI, Payfy’s model can fit standard ecommerce and certain crypto platform needs, subject to acceptance policies.