User actionStable

Generate GIROCODE

Presents an EPC/GIROCODE QR allowing the participant to prefill a SEPA transfer in their banking app.

Presented context

Generate GIROCODE

User Journey

User response

Vue d’ensemble

Presents an EPC/GIROCODE QR allowing the participant to prefill a SEPA transfer in their banking app.

Exemple

Show the customer a QR with IBAN, amount, and invoice reference to make bank transfer easier.

Key point A user action suspends the instance until the interaction is resolved. The User Journey presents the action; the node remains the orchestration contract determining its inputs and outputs.

Parameters 11

creditor_nameRequisstring

Beneficiary name encoded in the EPC payload of the SEPA-transfer QR.

creditor_ibanRequisstring

Beneficiary IBAN encoded in the EPC QR. This data remains subject to protections applicable to bank details.

creditor_bicOptionnelstring

Optional beneficiary BIC, encoded when required by the banking scenario or EPC scheme.

amountRequisamount

Transfer amount encoded in the QR, expressed in minor monetary units.

currencyRequiscurrency code

Transfer currency. The GIROCODE node supports the EPC contract in EUR.

reference_typeRequisenum

EPC remittance type used to encode the reference: structured or free-form.

payment_referenceRequisstring

Payment reference encoded in the QR to support later bank reconciliation.

titleRequisstring

Main title presented to the participant for this action in the User Journey.

descriptionOptionnelstring

Optional supporting text shown under the title to explain what is expected from the participant.

allow_replay_from_hereOptionnelboolean

Allows a participant to restart a replay from this interaction when the process enables that capability. Disable it when repeating the action would be dangerous or misleading.

replay_boundaryOptionnelboolean

Marks this interaction as a replay point of no return to bound earlier steps that can be replayed or reused.

Outputs 1

acknowledgedboolean

Whether the participant reached and validated the information or document step.

Behavior

The node encodes the beneficiary, EUR amount, and reference into a QR compliant with the EPC contract, then waits for the participant to confirm having initiated their action.

Limits and responsibilities

acknowledged does not prove that the bank executed or even accepted the transfer.
Reconciliation of the actual payment must rely on bank flows and the corresponding reference.