What payment gateways does Memo Genesis integrate with for one-time and recurring payments?

1. What the sources actually cover: Genesis (the payments gateway) versus Memo Genesis (the product)

The corpus contains two distinct veins of material: official technical repositories and documentation for a payments gateway called Genesis (including SDKs and API notes hosted on GitHub and emerchantpay docs) and investigative/consumer‑warning coverage of a product called Memo Genesis whose checkout practices are described as opaque and possibly scammy ^{[4] [1] [2] [3]}. The payment‑technology sources explain what a “Genesis” gateway can do (APIs, SDKs, alternative payment methods), while the Memo Genesis consumer reporting highlights a checkout page with little verifiable merchant information but does not enumerate the gateway providers used by that site ^{[1] [2] [3]}.

2. What the Genesis gateway (emerchantpay) supports for one‑time and recurring payments

Technical materials for the Genesis payment gateway — notably SDK repositories and emerchantpay’s integration documentation — show that Genesis exposes a Processing API, client libraries (Java, PHP, .NET, Node, mobile SDKs) and support for a range of payment flows and alternative payment methods that typically cover both single (one‑time) transactions and recurring or asynchronous flows via smart routing or hosted Web Payment Forms ^{[5] [6] [4] [1] [2]}. The emergent picture from the SDK READMEs and emerchantpay docs is that merchants using Genesis can implement one‑time card sales and also implement recurring/subscription flows using the gateway’s API and notification mechanisms ^{[1] [2]}.

3. Specific payment types listed in the Genesis SDKs (card + APMs)

The Genesis Java and other SDK READMEs explicitly list support for a variety of payment request types: generic financial operations (capture, refund, void) and an array of alternative payment methods including PayPal Express, P24, Neosurf and crypto endpoints like BitPay — indicating the gateway’s ability to process card payments plus many APMs that could be wired into one‑off or recurring models depending on merchant logic ^{[1] [7]}. These SDK entries document available transaction request types but do not map those types to a given merchant site’s checkout configuration; they describe gateway capabilities rather than any single integrator’s implementation ^[1].

4. Sticky.io’s note: Genesis gateway in that CRM routes specifically to eMerchantPay

A practitioner‑facing note in sticky.io’s help center is explicit that when using a “Genesis” gateway profile inside that CRM, the router will accept only emerchantpay (eMerchantPay) and that other gateways’ transactions will be declined — a concrete example where Genesis is tied directly to an underlying processor, which matters for merchants who want recurring billing reliability and chargeback handling ^[8]. That implementation detail illustrates that platform integrations can be restrictive: an off‑the‑shelf “Genesis” integration might map to a specific processor in some ecosystems ^[8].

5. Why this matters and what’s missing for Memo Genesis specifically

While the payments‑gateway documentation outlines what a Genesis/emerchantpay stack can support (one‑time and recurring card and APM transactions via APIs/SDKs), none of the inspected sources provides a verified mapping that Memo Genesis (the supplement) uses those gateway services or lists which external payment processors it deploys at checkout; the investigative report on the Memo Genesis funnel notes obfuscated merchant details on the payment page but does not name the gateway involved ^[3]. Therefore, a factual answer about “what payment gateways Memo Genesis integrates with” cannot be supplied from the available reporting without further, direct evidence from the Memo Genesis checkout or merchant account records.