Asystir Billing

Enter your API key to connect to billing and customer balances.

Billing

0 records

Customer Balances

Total paid and outstanding balance per contact.

Contact
Paid
Outstanding
Actions

New invoice

No client selected
Description
Qty
Unit
VAT %
Total
Net$0.00
VAT$0.00
Total$0.00

New payment

No client selected

Billing Setup

Configure the issuer data printed on Argentine invoices and the ARCA/AFIP Web Services connection.

Issuer invoice data

ARCA / AFIP Web Services

Point of sale

Mercado Pago payments

Configure credentials for generating Mercado Pago payment requests and receiving payment status through Webhooks or API polling.

Get Certification Help

This checklist explains what the tenant must do in ARCA before the API can request CAE numbers through WSFEv1.

  1. Confirm CUIT is active, Clave Fiscal level 3 or higher is available, and Domicilio Fiscal Electronico is configured.
  2. In ARCA, enable the services Administracion de Certificados Digitales and WebService de Facturacion Electronica.
  3. Create a private key locally and generate a CSR request file. Keep the private key secure; ARCA will not generate it for you.
  4. Upload the CSR in Administracion de Certificados Digitales, create an alias, and download the issued certificate file.
  5. Create a new point of sale for electronic invoicing using Web Services / RECE. Use a point of sale different from manual or online vouchers.
  6. Associate the certificate with the WSFE service and the issuer CUIT.
  7. Upload the certificate and private key in this setup view, choose homologation first, then test CAE requests before switching to production.
Official WSAA production certificate guide Official electronic invoice web services documentation WSFEv1 homologation service methods

Mercado Pago Setup Help

This checklist prepares the tenant to generate payment links or Checkout Pro preferences and receive payment notifications in the billing API.

  1. Create or open a Mercado Pago developer application in the Mercado Pago Developers dashboard.
  2. Copy the Public Key and Access Token for sandbox first. Use production credentials only after a successful test payment.
  3. Keep the Access Token and Client Secret only on the backend. They are used with the Authorization: Bearer header when the API creates payment requests or fetches payment details.
  4. Configure a Webhook URL for payment notifications in the application. Prefer Webhooks over old IPN flows.
  5. Copy the webhook secret/signature value so the API can validate the x-signature header before trusting a notification.
  6. When a webhook arrives, the billing API should use the payment ID to call Mercado Pago and fetch the full payment status before marking a billing payment as confirmed.
  7. Set a return/back URL so the payer can come back to your billing portal after completing payment.
Mercado Pago credentials documentation Mercado Pago Webhooks documentation Checkout Pro payment request documentation

New item

Placeholders: [current month], [past month], [current date]

Items

Select item

Select client