# Strings potx extracts that are deliberately not in a project's fr.po, one per
# line, each with the reason it is here. scripts/check-translations.php reads
# this file, so anything listed stops being reported: add a line only when the
# string is genuinely not worth an entry, never to quieten the check.
#
# Watchdog entries. potx extracts them because a logger call looks like any
# other call with a sentence in it, but a watchdog entry is not interface: it is
# read by whoever is diagnosing the site, often in a shared channel or an
# aggregator, and it stays in English on purpose. What the engine records and
# what a person is shown are two different sentences, and the ones a person is
# shown are in the catalogs.
#
# The test is WHO READS IT, not which call it sits in. Every entry below was
# checked to reach the site's log and nobody's screen: this project ships no
# Drush command, so no logger here writes to an operator's terminal. If a
# string here ever starts reaching a reader, it belongs in a catalog instead.
@caller has made more API requests than this site answers in one period. Raise the limits in the Kessai server settings if this consumer is simply busy.
A movement of payment @id was first asked 23 hours or more ago and never answered, so it is not sent again: Worldline may no longer know it, and would move the money a second time. Its operations show nothing carried out for it, so it is recorded failed. Check the transaction @reference in the merchant console, and record by hand anything it did.
Answered a request to move @asked for @kind with payment @id, which is for @standing: one of these is created per subject, kind, account and currency, so the one already standing is reused rather than a second hold placed or a second charge taken. Nothing was moved for the difference. A movement that has to stand beside this one needs a kind of its own.
Payment @id, taken with the payer gone, was first asked 23 hours or more ago and never answered, so it is not sent again: Worldline may no longer know it, and would charge the card a second time. It is recorded failed. Check the merchant console for a transaction with the merchant reference @merchant_reference, and give back anything it took.
Release skipped for payment @id: it is @state and holds nothing to release.
Payment @id was deleted while its provider session was opened, so the payer is not sent to that session.
Payment @id was @state while its provider session was opened, so the payer is not sent to that session.
Recorded the money a provider took on payment @id after it ended as given back outside kessai. Nothing was asked of the provider.
Cannot release the hold of payment @id: it is recorded authorized but the gateway of account @account cannot hold or release funds. The record and the gateway disagree; this needs looking at by hand.
Cannot capture payment @id: it is recorded authorized but the gateway of account @account cannot hold or claim funds. The record and the gateway disagree; this needs looking at by hand.
Capture skipped for payment @id: it is @state and holds nothing claimable. If the provider took the money, this needs reconciling by hand.
Cleared the stored payment method on payment @id locally: the gateway of account @account does not store payment methods, so there was nothing to delete at a provider. If the alias was created by another gateway it may still exist there and need removing by hand.
Cleared the stored payment method on payment @id locally: the gateway of account @account is not installed on this site, so nothing could be deleted at a provider. The alias may still exist there and need removing by hand.
Consumer @consumer answered @status to the @event notice for payment @id, so it does not know about it. Its payments are unaffected and it can still read them.
Could not acquire the payment create lock @name; proceeding on the in-flight record re-check alone.
Could not delete the stored card we did not request for payment @id: @message
Could not delete the stored payment method at the gateway for payment @id; keeping the local payment method id so the alias is not abandoned at the provider: @message
Could not record %channel.%action to the audit trail: @message
Could not release the rejected checkout charge for payment @id (@ref); it may still be on the payer's card, so check it in the back office and release it there: @message
Did not record the onward URL for payment @id: @url is not somewhere its payer may be sent, so the address the payment already held was kept.
Did not record the onward URL for payment @id: it is @length characters and the field holds @limit, so recording it would have failed the request the payer is in the middle of. They will be sent to the front page after paying instead.
Discarded a verified Worldline webhook for payment @id: it was signed with the webhook key of @signer and that payment was taken at account @account, and a notification settles only the payments of the account whose key signed it. Check that each Worldline account's webhook endpoint is registered against its own contract at the provider.
Expired @count due payment(s) without asking a provider: the gateway of account(s) @accounts is not installed on this site, so there was nobody to ask. If money may have moved on them, they need reconciling by hand.
Expired @count lapsed payment(s).
Expired @count payment(s) that went @hours hour(s) past their deadline without an answer: either the provider could not be reached, or the reconciliation budget never got as far as them. Check the gateway is reachable and configured, and raise kessai_engine.settings:reconcile_batch if the sweep is consistently behind. If the provider was down, these may need reconciling by hand.
Gave nothing back for payment @id: @refusal.
Handing payment @id off to the gateway of account @account failed (@kind): @message
Left @count due payment(s) pending: their provider could not be asked, or the run reached its reconciliation budget of @budget, so they were not written off unasked. The next cron run continues.
Payment @id failed, declined: @reason
Payment @id was reported authorized after its hold was released, and is taken to be that hold reported again. If the provider holds another transaction on it, release that one at the provider.
The provider gave no final answer about @movement of @amount on payment @id, so it stays pending and the next request for it asks again under the same key: @message
The provider gave no final answer about payment @id, so it stays pending and the next request for it asks again under the same key: @message
Payment @id has been handed off more times than this site allows in one period, so the payer was sent onward and nothing was opened at the provider.
Reconciled @count payment(s) with their provider instead of expiring them.
Recorded no movement for the money undone on payment @id: the caller named @amount, and only a positive amount moves money. If the provider took or held anything, nothing on this payment now says so, and it has to be reconciled against the merchant console by hand.
Refund skipped for payment @id: it is not in a captured state (@state).
Settled nothing for Worldline payment @id: another channel holds the lock and is settling it now, so this one did nothing rather than record the same movements twice.
Skipped @operation on payment @id: another caller holds the lock on the same money and is working on it now, so this one asked the provider for nothing and was told to try again. The payment is @state.
Skipped payment @id while forgetting stored payment methods: it is not a payment this site stores, so there is no row here to clear and no gateway here to delete its alias at. Whichever kessai holds it is the one that can.
Skipped payment @id while forgetting stored payment methods: it is not one of the consumer this engine acts for.
Skipped payment @id while forgetting stored payment methods: it names account @account, which this site reaches through no enabled remote, so there was no host to ask. The stored card may still be on file there. Whichever Kessai holds that account is the one that can forget it.
Skipped payment @id while forgetting stored payment methods: it was not read from a remote Kessai, so this client has no host to ask. The engine that holds it is the one that can forget it.
The Worldline SDK (wl-online-payments-direct/sdk-php) is not installed; the gateway is unavailable.
The expiry sweep hit its cap of @cap payments; more are still due and the next cron run will continue.
The provider reported payment @id @outcome, but the payment was already @state, so nothing was recorded. Release or refund it at the provider (reference: @reference), or settle it with the payer by hand.
Worldline @operation failed for payment @id: @class @message
Worldline @operation on payment @id gave no final answer yet; asking again under the same key will: @message
Worldline @operation on payment @id was carried out earlier, its answer lost; recorded from the transaction's operations.
Worldline checkout not started for payment @id: too little of its window is left to open a session.
Worldline had no outcome yet for payment @id (hosted checkout status @status).
Worldline hosted checkout returned no redirect URL or session id for payment @id.
Worldline named no amount on the created payment for @id, so the undo asks for the whole of it and is recorded against the payment amount (@amount) instead. Reconcile it against the merchant console.
Worldline payment @id rejected: the card expires before the deadline it must stay valid through, so a later hold or charge could not be made.
Worldline payment @id rejected: the created provider payment amount/currency does not match the local payment (expected @expected @currency).
Worldline payment @id was canceled by the payer at checkout.
Worldline refused payment @id, so it is marked failed: @detail
Worldline status fetch failed for payment @id; leaving it pending for the webhook to settle: @message

# Examples in an .api.php file, which document a hook and are never shown.
My gateway
A verified Worldline webhook names payment @id (provider payment @provider), which this site does not hold. If it is not another site's on the same contract, the money it reports is recorded nowhere here.
Worldline declined the stored-card payment @id, whose own answer never came back, so it is marked failed: @detail
Worldline payment @id rejected: the stored-card payment Worldline reported does not match the local payment (expected @expected), so it was given back and the payment is marked failed.
Worldline has no outcome yet for payment @id, so it stays pending: @detail
Left out payment @id that remote @remote answered with: it names account @account, which the remote is not recorded taking payments into.
Left account @account out of the accounts on offer: remote @remote could not say whether it takes a payment by then: @message
Worldline reports provider payment @provider accepted on payment @id, which already records provider payment @reference: the payer may have paid twice. Give @provider back at the provider.
