Update an eligible invoice from a verified payment result.
An active/default company iyzico connection, permissions and buyer data allow payment for the full TRY total of a sent/overdue invoice. The Vekilaw subscription payment account is not used for this collection. The flow and rates below are illustrative and create no payment.
01/04
5 stepsFive steps from an eligible invoice to a verified result
This illustration creates no checkout, callback or notification. Opening the provider page is not payment success; the verified result and final record must be read separately.
01/05
Firm
Sent or Overdue status, full amount/client matching, writable company and relevant grants are required. This status is not email-delivery evidence.
02/05
Firm
Start checkout with an active tenant merchant and complete buyer profile. A valid pending checkout may reopen for the same request; the link is not promised to open only once or remain valid indefinitely.
03/05
Client
An allowed provider address opens the external checkout; card fields in this flow belong to the provider form. Sharing is separate; do not assume automatic email/SMS dispatch.
04/05
Vekilaw
The callback is only a signal. The server retrieves the result with the saved tenant-provider context; success is not applied without signature, transaction, amount and currency validation.
05/05
Invoice
A verified successful result updates eligible payment/invoice records. Errors, review or uncertain outcomes are not assumed successful; lists, reports and notifications have separate conditions.
Eligible invoice
02/04
Online results are verified on the server
A pending or uncertain initiation may block another collection for the same invoice; do not bypass uncertainty with a new payment. Review the result and record. Repeated verified results do not close the invoice again; this is not unlimited provider retry/load acceptance. Paid-invoice editing is restricted; see invoicing.
03/04
The payment list tracks four states
Payment status and initiation uncertainty are distinct; a pending record does not prove the checkout link remains usable. Lists/collection metrics refresh through separate queries, not promised instant/atomic updates. Notifications depend on events, access, preferences and channel/provider conditions; delivery is not guaranteed.
- Pending
- Payment outcome is pending; neither link validity nor permission to initiate again is guaranteed.
- Under review
- The outcome is not yet final success/failure; this alone proves neither an active signature check nor collection.
- Successful
- An eligible provider-verified success; report refresh and notification delivery are separate.
- Failed
- A verified failure does not automatically mark the invoice paid. It is distinct from an uncertain network error; check the final record.
In this checkout flow, card number, expiry and security code are entered in the provider’s external form; Vekilaw API/form fields for this flow do not collect or store them. ISO/TSE certificate details have not been published; this flow is not certification evidence. Published operator information: Vekilaw; confirm current commercial/operational terms. See payment security and security.
04/04
What do people ask about online payments?
- 01/06
Which cards are accepted?
A valid tenant merchant and provider conditions are required; confirm accepted card/transaction options in the actual provider form. This source review is not live account/card acceptance or a successful collection test.
- 02/06
Who pays the commission?
Confirm the merchant account’s current provider agreement, commission and settlement terms separately; this page sets neither rates nor who bears them. Vekilaw subscription charges are separate; see pricing.
- 03/06
Is the payment link single-use?
Code may reopen an eligible pending checkout for the same actor/request; that does not mean the URL opens only once. An uncertain attempt may block another initiation. Verify the final record after link/network errors before starting again; keep the URL private.
- 04/06
What happens to the invoice if a payment fails?
A verified failure does not mark the invoice paid. A network timeout or uncertain attempt is not automatically a failure; review the current record and provider outcome. A new attempt requires current invoice/checkout eligibility.
- 05/06
Where does the payment notification arrive?
Notification processing depends on event/channel conditions; every-user or fixed-time delivery through in-app/email/SMS/WhatsApp/push is not guaranteed. Check the payment record separately; dashboard refresh is another query.
- 06/06
Where is the card information stored?
Card fields for this flow are in the external provider form; Vekilaw initiation/callback contracts contain no card-number, expiry or security-code fields. This does not verify every third-party retention policy or certification.