BridgeConnecteurStable

Create payment link (Bridge)

Creates or reuses a Bridge Payment Link for an existing Ormuz PSP payment without driving the user interaction.

PSP payment

Créer un lien de paiement (Bridge)

Payment link Bridge

extension_object_mapping

Vue d’ensemble

Create Bridge payment link is the low-level primitive to use when you want to control distribution of, or redirection to, Bridge yourself.

Like the high-level node, it starts from an existing psp_payment and reuses the link already associated with that payment when available.

Amount and currency come exclusively from the psp_payment.
The created output distinguishes creation from reuse.
With this low-level node, the callback_url is your responsibility.

Typical scenario

A merchant wants to send a bank-payment link through its own communication channel. It first creates the psp_payment, generates the Bridge Payment Link, then uses the secured URL in its custom experience.

Quick start

Use this node only when you need to control the Bridge link yourself; otherwise prefer bridge.collect_payment.

Provide

psp_payment existant
Payer identity
callback_url if the browser must return to your own experience

Do not duplicate

Amount
Currency
Primary payment reference

Configuration example

Parameter	Binding	Role
`psp_payment`	`payment`	Determines amount, currency, and reference
`callback_url`	`merchant_return_url`	Required only for your redirect scenario

Key point If your goal is simply to collect payment in an Ormuz journey, use bridge.collect_payment: it handles return and synchronization for you.

Process example

PSP payment

Créer un lien de paiement (Bridge)

Payment link Bridge + extension_object_mapping

Exemple simplifié d’utilisation de Créer un lien de paiement (Bridge) dans un processus Ormuz.

Data resolution

The node resolves this data from its inputs and Bridge context.

Data	Source or rule
Amount	`psp_payment.amount`.
Currency	`psp_payment.currency`.
Bridge reference	`psp_payment.id`.
Payer reference	`payer_external_reference` → `psp_payment.buyer_id` → `psp_payment.id`.
Lien existant	Bridge mapping already associated with the same `psp_payment`; the node rereads it and returns `created = false`.

Parameters 14

Contexte principal

Objects and configuration that determine the Bridge operation.

extension_config_idRequisref(extension_config:bridge)

Active Bridge configuration used for this operation. It determines the Bridge API credentials and environment; the merchant remains the merchant of the current process.

psp_paymentRequisPSP payment

Existing Ormuz PSP payment already created and belonging to the process. For Bridge payment nodes, its amount and currency are the source of truth and are not requested again as separate parameters.

Payer or user identity

Information used to identify the person or company interacting with Bridge.

payer_first_nameOptionnelstring

First name of the natural person making the payment. Use with payer_last_name when the payer is a natural person; these fields are unnecessary when payer_company_name identifies a company.

payer_last_nameOptionnelstring

Last name of the natural person making the payment. Use with payer_first_name when the payer is not specified as a company.

payer_company_nameOptionnelstring

Legal name of the company making the payment. Use this field instead of the payer_first_name / payer_last_name pair when the payer is a legal entity.

payer_emailOptionnelemail

Payer email address sent to Bridge when available. It helps identify the payer in the banking journey without modifying the Ormuz contact.

payer_external_referenceOptionnelstring

Payer business reference sent to Bridge. If absent, Ormuz uses psp_payment.buyer_id when available, then falls back to the psp_payment identifier.

Payment options

Choices applied to bank initiation and return from the Bridge experience.

callback_urlOptionnelurl

URL to which Bridge returns the browser after bank authorization. This parameter is intended for the low-level link-creation node; the bridge.collect_payment user action automatically handles its own return.

countryOptionnelenum

Country used to guide the Bridge bank-selection experience. Set it when the journey must be limited to a supported market (fr, es, de, or gb).

provider_idOptionnelinteger

Numeric Bridge banking-provider identifier to enforce. Leave this field empty to let the payer choose a bank in the Bridge journey.

sender_ibanOptionnelstring

IBAN of the source account when it must be enforced in the payment journey. This banking data is sensitive and should be supplied only when the use case requires preselecting the payer account.

labelOptionnelstring

Transfer label sent to Bridge and, depending on the bank, visible on the banking transaction. Use a business label understandable to both payer and beneficiary.

end_to_end_idOptionnelstring

End-to-end reference for the bank payment. Set it only if your system already has a stable payment reference that must be propagated to the bank.

expired_atOptionneldatetime

Date and time after which the Bridge payment link must no longer be usable. Use an ISO 8601 date consistent with the checkout validity period or business due date.

Outputs 3

Payment

Objects and state resulting from the payment lifecycle.

payment_linkBridge payment link

Current Bridge payment link, with its identifier, statuses, and payment information. Its hosted URL is classified as secret when present.

Session and traceability

Session identifiers, mappings, and creation indicators.

extension_object_mappingextension object mapping

Traceability link between the primary Bridge object produced by the node and the Ormuz object with which it is associated.

createdboolean

Whether the node created a new Bridge object. false means an already-associated object was found and reused.

Behavior

Look for an existing link

The node first checks whether the Ormuz payment is already associated with a Bridge Payment Link.

Reread or create

If it exists, the link is reread; otherwise Bridge receives a new request built from the psp_payment and supplied options.

Trace the mapping

The link is associated with the Ormuz payment and the mapping is returned with created.

Limits and responsibilities

This node does not redirect the user or wait for the end of the banking journey.
It does not by itself synchronize the final psp_payment status; use bridge.sync_psp_payment or the high-level node when needed.
An Ormuz payment already associated with another Payment Link is treated as inconsistent rather than silently remapped.

Troubleshooting

The link is reused even though I wanted to create a new one

That is the intended behavior for the same psp_payment. Create a new Ormuz payment if you genuinely need a new independent initiation.

Bridge rejects the payer identity

Provide either a company or the first-name/last-name pair; do not leave both modes incomplete.

The browser return does not work

Check that callback_url is a valid HTTP(S) URL and points to the experience you control.