Share your product
Create products, prices per currency and expiring payment links. Share them through WhatsApp, social media or your website without building a new store.
LunaPay® · Business payments
Receiving money is only part of the job. Know who paid, what for and what is still outstanding. Connect payments to the work you do every day.
Explore plans ↓Example merchant

Illustrative amounts, not currency conversion.
Choose how to pay
Illustrative demo · no payments are made
Link a product, customer, order or purpose to a payment link or checkout.
The buyer chooses from methods enabled for the account and transaction.
Use the verified transaction status, not a screenshot or the browser return.
Match the payment to your records. External updates require an integration.
From product to payment
Show the product, its photo and price before asking for payment. Buyers see who is selling, what they are buying and the options available for that transaction.
Create products, prices per currency and expiring payment links. Share them through WhatsApp, social media or your website without building a new store.
Checkout filters methods by account, country, currency and activation. Currency conversion needs a valid quote; changing the symbol does not convert the amount.
Every attempt keeps the order reference. Status is verified with the provider: a browser return or screenshot does not prove payment.
LunaPay® Checkout
A keyboard for your setup. A course for your next challenge. Two illustrative examples: a one-time purchase and monthly access. The operational checkout only shows combinations enabled for each transaction.
Example merchant

Illustrative amounts, not currency conversion.
Choose how to pay


Illustrative demo · no payments are made
Example merchant
Illustrative amounts, not currency conversion.
Choose how to pay


Illustrative demo · no payments are made
Each checkout identifies the business and the legal seller. Card details are captured through provider components or hosted pages; some transactions require leaving the website.
Product links with photos, one-time payments and subscriptions. Configure allowed methods; checkout only shows those eligible for the transaction, currency, country and account.
Planned integrations are listed below; listing does not prove live availability. Cards, transfers and crypto depend on the provider, account, contract and actual coverage.
Card or wallet available through an enabled processor. Subject to merchant, transaction and supported currency; not a standalone integration.
Card or wallet available through an enabled processor. Subject to merchant, transaction and supported currency; not a standalone integration.
Card or wallet available through an enabled processor. Subject to merchant, transaction and supported currency; not a standalone integration.
Cards and Mercado Pago checkout options for Argentine accounts in ARS. Recurring payments require subscription authorization.
Card or wallet available through an enabled processor. Subject to merchant, transaction and supported currency; not a standalone integration.
Visa, Mastercard, American Express and Cabal depending on the account. Three interest-free installments only with eligible online campaigns, local credit cards and transactions.
Domestic bank transfers with payment references and reconciliation. An identified transfer is not an automatic debit.
USD transfers to an enabled US account; ACH and Wire are different rails. Requires an enabled receiving account, bank instructions and confirmation flow. This is not a withdrawal channel or a guarantee of availability. IBAN identifies the account; SWIFT is not limited to Europe.
Transfers to an IBAN account: SEPA in EUR or SWIFT, subject to bank and eligibility. Requires an enabled receiving account, bank instructions and confirmation flow. This is not a withdrawal channel or a guarantee of availability. IBAN identifies the account; SWIFT is not limited to Europe.
Cards and international currencies supported by the account. Subscriptions require the appropriate product and consent.
Payments and subscriptions depend on product, country and account. Guest card checkout is not guaranteed in every case.
Payments through Binance Pay using supported assets. Renewals require fresh authorization unless a recurring debit product is contracted and verified.
Crypto payments with defined asset, network and confirmations. This does not enable automatic debits from any external wallet.
BTC · ETH · USDT · USDC · BNB · XRP · SOL · TRX · ADA · DOGE · LTC · BCH · DOT · LINK · AVAX · TON · DAI · UNI · XLM · ATOM
This is an integration catalog, not a list of services active for every business. Activity approval, the provider account and technical verification determine what appears at checkout. Payment currency and payout channel are separate decisions.
Cards and wallets are not processors. Available brands depend on the account and transaction; a logo does not establish enablement.
Illustrative catalog, not a ranking. Availability depends on asset, network, account, country and transaction. Not all these assets are catalog pricing currencies or enabled for collection or withdrawal.
Automatic recurring charges only where integration and authorization exist. Manual renewals are also supported. A free first month requires the applicable conditions and consent; it never turns into a charge without a mandate.
An eligible ARS purchase with a local credit card may use three installments under an enabled ecommerce campaign. This is one sale, not a subscription. The buyer's total remains unchanged; displaying a logo does not enable the offer.
Choose the workflow your business needs. Rates apply to the gross amount actually confirmed.
$0.00fixed monthly fee
8% + VAT on the fee where applicable
Create my accountCompatible methods, subject to enablement
Withdrawal channelsEnabled local CBU/CVU
Invoicing with your own CUIT through Afip SDK
Dashboard, products and standard checkout · Own CUIT without switching to 29%
$0.00fixed monthly fee
8% total · no VAT added on top
Create my accountCompatible methods, subject to enablement
Withdrawal channelsEnabled CBU/CVU, ACH/Wire and crypto
Invoicing with your own CUIT through Afip SDK
Domestic and international channels when enabled · Own CUIT without switching to 29%
$0.00fixed monthly fee
29% final · no VAT added on top
Create my accountCompatible methods, subject to enablement
Withdrawal channelsEnabled CBU/CVU, ACH/Wire and crypto
Sales under the approved Paradise entity
API and advanced checkout · Initial 71% commercial settlement share
These are not guaranteed bank net amounts: statutory withholdings and documented adjustments may apply. No additional commercial charges by default. Pro requires activity, issuer and contract review; it is not a tax exemption.
Transparent numbers
Compare all three plans using the same confirmed gross amount. No fixed monthly fee or additional commercial charges by default.
No thousands separator. Up to two decimal places, using a dot or comma.
Estimated monthly gross: ARS 100,000.00
Initial settlement amount per saleARS 90,320.00
Monthly settlement: day 15
Initial settlement amount per saleARS 92,000.00
Monthly settlement: day 7
Initial settlement amount per saleARS 71,000.00
Monthly settlement: day 7*
Commercial estimate, not a binding quote or guaranteed bank proceeds. Basic assumes 21% VAT on the fee, not on the entire sale. Global deducts 8% total and Pro 29% final; 29% is not a VAT rate. Statutory withholdings, reserves, refunds and documented adjustments are excluded.
Changing currency neither converts amounts nor enables a payment method or payout. Sales tax and contributor documentation are determined separately. Pro requires contractual approval.
Commercial rounding to cents per sale; the month multiplies that result by the number of identical sales. Days 7 and 15 are monthly dates, not T+7/T+15 or a guaranteed transfer.
* The initial cutoff covers sales from the previous calendar month. Basic settles on the 15th; Global on the 7th; Pro starts on the 7th under a versioned contract policy. Holidays move to the channel's next business day. Unreleased funds, reserves and adjustments may affect availability. A prepared settlement is not an executed transfer: withdrawal requires a request or mandate and actual channel confirmation.
The initial cutoff covers sales from the previous calendar month. Basic settles on the 15th; Global on the 7th; Pro starts on the 7th under a versioned contract policy. Holidays move to the channel's next business day. Unreleased funds, reserves and adjustments may affect availability. A prepared settlement is not an executed transfer: withdrawal requires a request or mandate and actual channel confirmation.
Clear responsibilities
Basic and Global: the merchant remains the seller and invoice issuer. Afip SDK automation uses the merchant's own CUIT, with valid representation, certificates and ARCA authorization. It does not activate the 29% rate.
In Basic and Global, configure your CUIT, tax status and point of sale. You remain the seller; this automation does not move you to the 29% plan.
The Afip SDK connection requires delegation or certificates and valid ARCA permissions. LunaPay® does not ask to store your personal tax password.
Follow pending, authorized or rejected issuance and its documentation. An approved payment does not mean the invoice is authorized.
Pro: the Paradise entity that legitimately acts as seller invoices its approved sales. A documented commercial relationship with the product or service supplier is required. This is not replacing the CUIT on a PDF, and it does not eliminate the contributor's personal obligations.
We review identity, activity, catalog and the contributor relationship. You can apply without a company, but that does not automatically enable payments.
The Paradise entity actually selling the transaction assumes the agreed responsibilities for that sale, invoicing, refunds and disputes.
The sale, contributor supply, taxes and settlement are documented separately. The contributor’s personal obligations do not disappear.
Confirms a transaction with the provider; it is not a fiscal authorization.
Documents the correct issuer’s sale, with applicable requirements and authorizations.
Details fees, adjustments and the commercial balance. It does not confirm a bank transfer.
An invoice or receipt is not equivalent to fiscal authorization. A confirmed payment can have a pending or rejected tax invoice. Technical configuration does not mean operational enablement.
Read the legal documentation ↗These scenarios describe how a workflow could be designed. Registration does not automatically approve an industry. Each activity and capability requires review. The current operational catalog is limited to technology products and services.
A manager identifies the September payment for unit 4B.
Unit and period, due dates, partial payments and outstanding balance.
Integrate the account balance and exports with property management software; there is no built-in building-fee module.
A family pays enrollment, tuition and an extracurricular activity.
Match the student and payment purpose even when someone else pays; track outstanding fees.
Integrate student records, fee categories and unpaid obligations with the education system.
A member pays a monthly membership and a tournament entry.
Separate memberships, renewals and additional activities to check payment status.
Connect member records and access rules. Renewal does not imply automatic debit.
A studio collects an advance and two project milestone payments.
Match payments to customers, quotes or stages; domestic or international payments where supported.
Integrate quotes and milestones. Activities and international channels require approval.
A shop confirms a transfer before releasing an order for shipping.
Share product links with photos, link the payment to an order and confirm before dispatch.
Product links exist; automatic order updates require a store integration and an enabled payment method.
A customer renews web hosting or a support plan.
Due dates, renewals and service updates. Automatic subscriptions and manual renewals are separate modes.
Integrate service provisioning. Automatic debit requires a compatible provider, mandate and enablement.
A customer pays a venue deposit and later pays the balance.
Record the advance, remaining balance, reservation expiry and refunds.
Connect availability, bookings and cancellation rules; no booking engine is included.
A business partially pays several supplier invoices.
Identify the customer, allocate payments to documents and reconcile the customer account.
Integrate the ERP and document allocation. A payment does not authorize a tax invoice.
Someone pays an appointment deposit or a package of sessions.
Associate payments with the service and handle confirmations and cancellations without clinical information.
Integrate scheduling with minimal references; never send diagnoses or medical records into the payment flow.
An organization sells conference tickets.
Link confirmed payments to registration and access delivery.
Ticket issuance and admission require integration with the event platform.
A supporter makes a one-time or periodic campaign contribution.
Identify the campaign, track the contribution and deliver the appropriate receipt.
Validate the activity and documentation; integrate campaigns. Periodic contributions do not guarantee automatic debit.
An application adds payments for multiple service providers.
Merchant onboarding, beneficiary identification and transaction reconciliation.
Requires platform agreements and capabilities. Automatic fund splitting is reserved for a later phase.
LunaPay®
If your workflow needs an integration, share the context. We keep your inquiry and assess the scope before promising enablement.
Onboarding requires verification and manual approval. These examples do not establish authorization to operate in those industries.