SEPA Direct Debit B2B workflows

Check a bank’s SEPA B2B participation in your workflow

Add an EPC register check to your B2B direct debit preparation. IBAN-Test returns the bank’s SEPA B2B participation status with the IBAN validation response, so your system can distinguish confirmed matches from cases needing review.

40 countries

Bank-directory checks where source data is available

115 IBAN formats

Country rules, length and check digits

REST API

Authenticated requests and JSON responses

Why this check matters

Make the bank-participation check an explicit part of preparation

Check the B2B scheme separately

Read the bank’s B2B status independently from SEPA Core, credit transfer and instant credit transfer results.

Keep uncertain results visible

Use the returned status and reason to distinguish a confirmed register match from an unknown result.

Combine the result with IBAN validation

Read the bank-participation fields from the IBAN validation response and keep them separate from the formal IBAN result.

From input to a usable result

How the check fits into your workflow

Step 1: Validate the IBAN

Submit the IBAN to the authenticated validation endpoint. Available bank information is used for the separate SEPA register checks.

Validate the IBAN and use available bank information for a SEPA register lookup
Read B2B participation separately from Core, SCT and SCT Inst

Step 2: Read the B2B register result

Evaluate details.sepa.sddB2b.status and reason. Confirmed means an unambiguous, current EPC register match; unknown means participation could not be confirmed.

Step 3: Apply your collection policy

Continue your bank-participation review with a confirmed result, or route an unknown result for clarification. Check the account’s eligibility and the mandate through your own collection process.

Use confirmed or unknown bank participation to guide your internal review

See the API in context

A separate result for the scheme your collection uses

The response exposes sddCore, sddB2b, sct and sctInst independently. Your B2B collection workflow can read the B2B field without inferring it from Core or from a valid IBAN.

An authenticated validation request

curl -X POST "https://www.iban-test.eu/api/v2/iban/validate" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  --data '{"iban":"DE89370400440532013000"}'

Published reference IBAN for integration examples.

SEPA B2B response excerpt

{
  "details": {
    "sepa": {
      "sddB2b": {
        "status": "confirmed",
        "reason": "matched"
      }
    }
  }
}

Illustrative excerpt. Evaluate the complete response and HTTP status.

What the register result confirms

The lookup checks bank participation against EPC participant registers. It does not confirm a mandate, account-level direct debit eligibility or the success of a collection. An unknown result is not proof that the bank does not support B2B.

Integration packs: PHP · Python / CSV · Excel / Power Query · Google Sheets / Apps Script · n8n · SEPA participation

SEPA bank-participation guide · All integration guides · API documentation

API plans

Choose API capacity for your SEPA checks

Compare the current API packages and select the allowance that fits your workflow.

Monthly figures are calculated over 30 days. The limit applies per 24 hours.

* Offers only for commercial use, prices excl. VAT.

Before you integrate

Questions about this use case

Does confirmed mean my direct debit will succeed?

No. Confirmed describes an unambiguous, current bank match in the EPC participant register. It does not confirm account eligibility, a valid mandate or collection success.

Read the SEPA bank-participation guide

Does unknown mean the bank does not support B2B?

No. Unknown means participation could not be confirmed. Read the reason and route the case for review; missing or ambiguous data can produce an unknown result.

Understand SEPA statuses and reasons

Can I infer B2B participation from SEPA Core?

No. The API checks sddCore and sddB2b independently. Read the result for the scheme your workflow uses.

See the four independent SEPA checks

Do I need a separate BIC validation request?

The SEPA participation fields are included in the IBAN validation response when bank information is available. The separate BIC validation endpoint does not return these SEPA fields.

View the API documentation

Your next integration

Bring the B2B register check into your collection workflow

Choose your API allowance and use the separate B2B status alongside the IBAN validation result.

Choose your API plan