How MakePay works with Facturama
A Facturama CFDI records fiscal facts, but its original total does not tell you everything a customer owes today. Payments received elsewhere, credits and adjustments still matter. MakePay keeps that distinction visible: you confirm the current receivable before approving an invoice collection.
The connection separates customer checkout, original-invoice payment pairing and fiscal issuance. You can collect an existing invoice without immediately issuing another fiscal document. Separately reviewed payment complements and new-invoice rules are optional, and all financial automation starts disabled.
Before you connect
- Your own Facturama API Web username and password for the intended issuing RFC and environment. No MakePay OAuth app registration is required.
- Current receivable records, including external payments and adjustments, plus configured MakePay merchant settlement settings.
- For fiscal issuance: the actual native branch, series, payment form, receiver and tax details. Real company payments require a production connection.
Set up Facturama with MakePay
- 01
Confirm the issuing taxpayer
Open MakeCrypto → Bookkeeping → Integrations → Facturama. Check the API Web credentials and confirm the returned RFC, fiscal name, regime, postal code and environment. Production and sandbox accounts are separate. Credentials are stored encrypted; connecting alone enables no collection or fiscal issuance.
- 02
Approve the actual amount owed
Import and review the existing invoice and fiscal payment evidence. Enable approved payment links, enter the current receivable and confirm the collection, including external payments. An active CFDI or PUE label is not independent proof of an unpaid balance. Incomplete or conflicting evidence stays in review.
- 03
Share the original collection link
The approved link lasts 12 hours and retains its original issuer, invoice, amount and currency. Opening it checks the approval and fiscal evidence again. A matching confirmed MakePay payment pairs with that original invoice in Bookkeeping. Share the link yourself; the connector does not automatically insert it into a Facturama PDF or email.
- 04
Choose fiscal issuance separately
Review a payment complement with the actual source, valuation, receivable, dates, partiality and tax allocation. Alternatively, authorize an eligible future MXN CFDI 4.0 PPD collection's exact receipt rule before payment. New invoices for unpaired confirmed payments use their own customer, product, valuation and fiscal approval workflow.
What happens when a customer pays
A receipt rule belongs to one original collection
Automatic receipts require exclusive collection through the approved link, its exact tax template and your confirmation that MakePay's first recorded payment confirmation represents beneficiary receipt time in your accounting process. Choose the time zone explicitly. External payments, changed invoices, late confirmations or different amounts need individual review. If the time policy does not fit your process, review the actual receipt date manually.
Future unmatched payments can follow an approved invoice rule
Choose a native Facturama customer and product, exact fiscal template, amount policy and one MakePay link or connected wallet/chain/asset. Wallet rules require your fixed MXN valuation. Only future eligible confirmations can queue invoices; there is no historical backfill or customer guessing. Pause rules and review out-of-policy payments in Bookkeeping.
Recovery retains the original fiscal operation
MakePay stores the approved request, source, reference and dates before dispatch, then compares the resulting native document and XML. An uncertain response triggers lookup of that original reference rather than another automatic issuance. Optional in-app notifications report matches, verified issuance and review or sync problems.
Check these connection limits
- Current issuance uses CFDI 4.0 and Payments 2.0. Supported historical formats can inform review, while unsupported or incomplete evidence cannot authorize financial actions. Fiscal history cannot prove the absence of external payments.
- Automatic receipts cover an explicitly authorized original MXN PPD collection. Other eligible payments use individual review; cross-currency invoice/payment receipt conversion is unsupported.
- Wallet expense exports and expense-file uploads are unavailable through this connection. A credit note is not an expense. Refunds, cancellations and corrections require separate handling.
- Document checks are not SAT certification, full XML-schema or signature validation, or independent tax approval. Review your fiscal treatment and the full setup guide before enabling issuance.
Setup resources
Follow the detailed connection guide and your software’s own account requirements. Configure merchant settlement before sharing a customer invoice.
