Curated market guide
Guatemala PSP routes to verify first
Which PSPs, acquirers, gateways, and local payment routes should a merchant ask first for Guatemala?
Acquirer / merchant-services route
Prioritize a local acquirer or bank merchant-services route when card acceptance is the main checkout requirement.
Do not claim a Guatemala entity is or is not required. Guatemala onboarding can depend on bank, acquirer, wallet, applicant type, and product; verify with the provider and counsel before promising access.
- Can you onboard my current company, or is a Guatemala entity, local bank account, or local tax profile required?
- Which card-present, card-not-present, payment-link, and gateway options are available?
- How are chargebacks, refunds, installments, and fraud controls handled?
Gateway / orchestration route
Prioritize a gateway when you need API access, plugins, or a bank-integrated checkout layer.
Do not claim a Guatemala entity is or is not required. Guatemala onboarding can depend on bank, acquirer, wallet, applicant type, and product; verify with the provider and counsel before promising access.
- Is the API available for Guatemala merchants and my industry category?
- Which bank or acquiring contract is required before production access?
- What technical certification, support path, and production approval are required?
Wallet acceptance route
Prioritize a wallet or cash/wallet network when customers prefer app-based, agent-network, or non-card payment flows.
Do not claim a Guatemala entity is or is not required. Guatemala onboarding can depend on bank, acquirer, wallet, applicant type, and product; verify with the provider and counsel before promising access.
- Is merchant collection available for online, in-app, QR, or cash-in/cash-out flows?
- Can the provider support refunds, reconciliation, and customer support at the merchant level?
- Which official merchant form or partner channel should be used?
Cards via local acquirer or bank merchant-services provider
Cards remain the baseline online route for many merchants, but the commercial onboarding path is provider-specific and should be checked before integration work.
Do not claim a Guatemala entity is or is not required. Guatemala onboarding can depend on bank, acquirer, wallet, applicant type, and product; verify with the provider and counsel before promising access.
- Use official bank/acquirer merchant pages, developer portals, or contact forms; do not assume a generic website contact is an onboarding inbox.
- Can you onboard my current company, or is a Guatemala entity, local bank account, or local tax profile required?
- Which card-present, card-not-present, payment-link, and gateway options are available?
BAC API or bank-integrated gateway route
BAC's regional API portal and Guatemala business presence make it a route to evaluate when bank-integrated APIs matter.
Do not claim a Guatemala entity is or is not required. Guatemala onboarding can depend on bank, acquirer, wallet, applicant type, and product; verify with the provider and counsel before promising access.
- Register or use the official developer/support route and ask what Guatemala-specific contract or plan is required.
- Can you onboard my current company, or is a Guatemala entity, local bank account, or local tax profile required?
- Which card-present, card-not-present, payment-link, and gateway options are available?
Documents to prepare
- Company registration certificate and operating entity details.
- Beneficial-owner, director, and signatory identity documents.
- Business website/app URLs, product description, refund policy, terms of service, and restricted-category explanation where relevant.
- Bank account, settlement currency, tax/VAT/GST information, and expected processing volume.
Questions to ask
- Can my current merchant entity onboard, or is a local company or bank account required?
- Which local payment methods are live for my business category and customer flow?
- What documents are required for KYB, technical review, and production approval?
- How are refunds, chargebacks, reconciliation files, reserves, FX, and payout currencies handled?
- Which public email, form, dashboard, or partner manager should be used for merchant onboarding?
If the official contact route is unclear
Use official form/contact page first; if there is no public sales inbox, use LocalPayMap WhatsApp fallback for routing help.
- Which local payment methods are live for my business category and customer flow?
- What documents are required for KYB, technical review, and production approval?
- How are refunds, chargebacks, reconciliation files, reserves, FX, and payout currencies handled?
- Which public email, form, dashboard, or partner manager should be used for merchant onboarding?
Route comparisons
BAC Credomatic Guatemala vs Banco Industrial (Ecosistema Bi / Link Bi) in Guatemala
BAC API Route vs Wallet or Agent-Network Collections in Guatemala
How local customers usually pay
Guatemala is a mixed market where cards, bank transfers, payment links and cash-style networks can all matter. BAC Credomatic, Banco Industrial, Banco G&T, Ecosistema Bi and Akisi/PRONET-style routes point to a landscape where bank relationships and local collection networks still matter. For small merchants, the first issue is not whether a payment logo exists, but whether the provider can onboard your entity and give reliable payment confirmation. Cash-in or agent-style payments can help customers without cards, while cards and bank transfers serve formal ecommerce. Ask providers to explain settlement files, refunds and failed-payment handling for each route.
- Cards through local acquiring or a gateway. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.
- Bank transfer and payment-link routes for domestic buyers. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.
- Cash collection or agent-network options where the provider supports them. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.
Payment methods to check first
For Guatemala, begin with the methods that match real customer behavior, then map each one to a provider that can actually onboard your merchant. Current public records point to Mobile money, Digital wallet, General commerce, Cash collection, Instant payment and Bank transfer, but availability can vary by PSP, entity type and industry.
- Start with the payment method customers already recognize, not the provider with the longest logo wall.
- Check whether the method supports online checkout, payment links, QR, app redirects, refunds and clear transaction references.
- Keep one fallback method for buyers who cannot or will not use cards.
- Document which method is mandatory for launch and which can wait for phase two.
What to do if you do not have a local company
Do not assume a foreign company can use the same route as a local merchant in Guatemala. Some PSPs can onboard overseas entities, some require a local company and local bank account, and some support only selected industries. The cleanest first email states your incorporation country, product, website, expected volume, average order value, customer location, settlement currency and refund model.
- Ask whether foreign entities are accepted directly or only through a local subsidiary, distributor or merchant-of-record arrangement.
- Confirm local company, tax ID, local bank account, local director, licence and proof-of-address requirements.
- Ask which settlement currencies and payout countries are supported for your entity.
- Get the onboarding answer in writing before promising a local method to customers.
PSP and four-party provider screening
Use provider discovery to separate customer-facing payment brands from the companies that can legally process and settle funds. Public PSP/contact leads for Guatemala currently include Akipuedo, Akisi (PRONET S.A.), BAC Credomatic API Center, BAC Credomatic Guatemala, Banco Agromercantil de Guatemala, S.A. and Banco Azteca de Guatemala, S.A.. Compare them by eligibility, method coverage, operational support and documentation quality rather than headline pricing alone.
- Akipuedo: Payment provider. Verify live coverage for Cash voucher, Bill payment and Agent network (12,000+ points), entity eligibility, pricing, settlement and support before treating it as a launch option.
- Akisi (PRONET S.A.): Wallet operator. Verify live coverage for Wallet P2P, Bill payments, Remittance collection, Merchant payments, Nano-credit and Cash-in agent network, entity eligibility, pricing, settlement and support before treating it as a launch option.
- BAC Credomatic API Center: Acquirer / merchant services. Verify live coverage for Bank APIs, Merchant POS support, Cards and Payment services, entity eligibility, pricing, settlement and support before treating it as a launch option.
- BAC Credomatic Guatemala: Bank merchant services. Verify live coverage for Visa, Mastercard, Debit and credit cards, Online gateway, Bank transfer and Multi-currency (USD and local), entity eligibility, pricing, settlement and support before treating it as a launch option.
- Banco Agromercantil de Guatemala, S.A.: Bank merchant services. Verify live coverage for cards and bank transfer, entity eligibility, pricing, settlement and support before treating it as a launch option.
- Banco Azteca de Guatemala, S.A.: Wallet operator. Verify live coverage for cards, wallet and bank transfer, entity eligibility, pricing, settlement and support before treating it as a launch option.
- Banco de Antigua, S.A.: Bank merchant services. Verify live coverage for cards and bank transfer, entity eligibility, pricing, settlement and support before treating it as a launch option.
Settlement, currency, refunds and disputes
Treat all pricing and settlement information for Guatemala as preliminary until confirmed by the official provider or contract. Fees, payout timing, rolling reserves, FX, chargeback costs and refund rules can change by industry, volume, risk review, settlement currency and integration route.
- Ask for transaction fee, fixed fee, refund fee, chargeback fee, payout fee, FX spread, reserve policy and minimum monthly or setup charges.
- Confirm payout timing, settlement currency, settlement account country, failed-payout handling and reconciliation file fields.
- Check whether refunds must return through the original method and whether partial refunds are supported.
- For cards, confirm dispute workflow, evidence deadlines, chargeback fees and fraud-monitoring rules.
Compliance and operating checks
Before launch in Guatemala, prepare KYB and risk material as if the provider will ask for it. Most delays for new merchants come from unclear ownership, unsupported industries, missing licences, incomplete websites, weak refund policies or settlement accounts that do not match the merchant record.
- Prepare company registration, ownership, director ID, website/app URL, product description, terms, privacy policy and refund policy.
- Disclose regulated products, digital content, subscriptions, marketplace activity, high-risk categories and cross-border fulfilment.
- Ask how the provider screens sanctions, fraud, AML risk, chargebacks and customer complaints.
- Keep sensitive or restricted markets at compliance-review level; do not use unofficial workarounds.
Questions to ask service providers
Send a concise written checklist to every Guatemala PSP or aggregator so responses can be compared side by side. The goal is to expose hidden entity, settlement, support and technical gaps before engineering work begins.
- Which payment methods are live today for my exact merchant entity, industry and customer geography?
- Do you support hosted checkout, API, plugin, payment links, webhooks, sandbox, refunds and reconciliation exports?
- Who is the merchant of record, who handles chargebacks and who owns customer support for failed payments?
- What documents are requested, how is approval reviewed, and what would cause rejection?
- Can you provide official links for pricing, settlement terms, developer docs and support escalation?
Common beginner mistakes
The most common mistake in Guatemala is treating payment acceptance as a logo checklist. Local conversion depends on customer habit, provider eligibility, settlement flow, refund support and operational reliability. A cheaper-looking route can become expensive if it cannot settle where you need, cannot refund cleanly or cannot support the methods buyers expect.
- Choosing cards only when wallets, mobile money, bank transfer, QR or cash-style routes are normal for local buyers.
- Building against an API before KYB, entity and settlement eligibility are confirmed.
- Ignoring refund and dispute flows until the first customer complaint arrives.
- Comparing providers without asking the same written questions of each one.
Questions merchants ask
Which payment methods should a new merchant check first in Guatemala?
Start with Mobile money, Digital wallet, General commerce, Cash collection, Instant payment and Bank transfer. Then confirm which provider can support your entity, industry, customer geography, settlement currency and refund model.
Can a foreign merchant accept local payments in Guatemala without a local company?
Sometimes, but it must be verified provider by provider. Ask whether a local entity, local bank account, tax ID, licence, local director or merchant-of-record route is required.
Which PSPs or aggregators are worth screening for Guatemala?
Public leads include Akipuedo, Akisi (PRONET S.A.), BAC Credomatic API Center, BAC Credomatic Guatemala, Banco Agromercantil de Guatemala, S.A. and Banco Azteca de Guatemala, S.A.. Treat them as a shortlist for outreach, not as confirmed eligibility or complete market coverage.
Can I use public fee pages as a final quote?
No. Public fees are screening context only. Final pricing can vary by country, industry, volume, risk review, settlement currency, FX, reserves and contract terms.
What operational questions should I ask before integration?
Ask about onboarding documents, restricted industries, live payment methods, checkout flow, webhooks, sandbox, refunds, disputes, chargebacks, reconciliation files, settlement timing and support escalation.
What should I do if the provider has no public sales email?
Use the official contact form, support page or developer contact route, and send a short brief with your entity country, product, volume, currencies and required payment methods.