# Authorize EBICS payments via email

EBICS Stage B: email 2-factor authorize (starter only), then scheduled SCT/XCT upload with low / medium / large amount risk paths.

After invoices are queued for payment on an EBICS batch, **Authorize via email** is the explicit **2-factor** step: Cortena emails a confirmation link to the starter. Only that person can confirm while signed in; Cortena then **schedules** the pain.001 upload (SEPA or international) to the bank via EBICS.

For the full journey (bank request → INI letter → activation → payments), see [EBICS with Cortena](https://help.cortena.ai/guides/integrations/ebics).

**Who this is for:** Users with **Export to payment** on workspaces that use EBICS banking and payment processing.

## 1. Queue invoices for payment

1. From Payables, **Send for payment** so invoices join an EBICS payment batch (Cortena queue: Stage A).
2. Open **Payables → Payments**.
3. Find the EBICS batch. The rail hint shows that EBICS uses email authorize for SEPA / international upload.

Nothing is sent to the bank yet.

## 2. Start authorization by email

1. On the batch, click **Authorize via email**.
2. Cortena emails [**payment-authorizations@cortena.ai**](mailto:payment-authorizations@cortena.ai) to the starter with each invoice, supplier, and amount.
3. Open the link while signed in **as that same user**.

## 3. Accept on the authorize page

1. Review the transfers on **Authorize EBICS payment**.
2. Confirm with **Authorize and send via EBICS**.
3. Status moves to sending / scheduled; the EBICS worker uploads SCT (SEPA) or XCT (international) pain.001 according to Cortena’s risk scheduling.

Only the person who started authorization can accept. If another user is signed in, confirmation stays blocked.

## After confirmation: scheduling by amount

| Path | What happens |
| --- | --- |
| **Low** amounts | Handed over to the bank **promptly** |
| **Medium** amounts | **Delayed a few hours** so there is time to roll back if needed |
| **Large** amounts | Also reviewed by the **Cortena risk team** before the bank upload proceeds |

## Tips and limitations

- Do not confuse this with FinAPI **Authorize** (Web Form) or pain download. EBICS Stage B only runs after email accept.
- Your bank must have enabled payment orders (and non-SEPA if you need international) on the EBICS contract. See [EBICS with Cortena](https://help.cortena.ai/guides/integrations/ebics).
- Related: [EBICS with Cortena](https://help.cortena.ai/guides/integrations/ebics), [Payment status](https://help.cortena.ai/guides/invoices/payment-status), [FinAPI](https://help.cortena.ai/guides/integrations/finapi), [SEPA vs international payment batches](https://help.cortena.ai/guides/integrations/sepa-international-payments).

## Quick reference

| Task | Where |
| --- | --- |
| Start email authorize | Payables → Payments → Authorize via email |
| Confirm | Link → Authorize and send via EBICS (starter only) |