Payments, cards and documents
Use Payments to understand charges and refunds. Use Documents for invoices, acts and recorded consents. These screens show only the records of your customer account; they do not contain the conversations or files stored inside an AiHummer instance.
Payment history
Each row shows the date, purpose, amount and current status. Open a row when you need its receipt or a clearer failure result.
- Pending — the bank or invoice payment has not finished yet.
- Paid — the charge is complete.
- Failed — no successful charge was recorded; retry from the order or subscription screen.
- Refunded — the refund was recorded. The bank may need additional time to show the money on the card statement.
A fiscal receipt link appears on a paid card transaction when it is available. The receipt is separate from an invoice or act.
Linked card
Card details are entered on the bank’s secure page. The portal displays only a masked card reference. A linked card may be used for automatic renewal.
Before unlinking a card, check whether an active subscription still uses automatic renewal. If no usable payment method remains, the next automatic charge cannot complete. Add or link the intended card through a payment flow, then remove the obsolete card.
Invoices and acts
The Documents list shows the document type, number, date and amount.
- Use the type and period filters to find the record.
- Open or download its PDF.
- Check that the payer details match the confirmed requisites in Profile.
An invoice is a request for payment. An act confirms the completed service or transfer for the applicable period. An invoice for a company may also contain an SBP payment QR code. Documents keep the requisites that applied when they were issued; changing profile data does not rewrite an old document.
Consents
The same section records the mandatory consents accepted during registration, including their date. These records are informational and cannot be edited from the document list.
If something is missing
- The payment remains pending: refresh after the bank or invoice payment has completed. Do not create repeated payments while one is still processing.
- A charge failed: check the bank message and card limits, then retry from the action that created the charge.
- No fiscal receipt link: wait until the payment is paid and the receipt has been issued. Contact support with the payment date and amount if it still does not appear.
- Wrong requisites on a new document: correct or request correction of the requisites before the next document is issued.
- A refund is not on the statement yet: compare the portal status with the bank’s processing time; the portal’s refunded status means the refund was initiated or recorded, not that every bank has posted it immediately.
Next
- Order and payment — create the first payment.
- Billing lifecycle — what happens from checkout to renewal or refund.
- Profile and requisites — payer details.