Gasóleo Bonificado

📘

Your account must be enabled for this feature

🚧

Limited to certain acquirers in Spain

👍

Available soon

Gasóleo Bonificado is processed as a card brand within the standard nexo card-payment flow. It does not introduce a new nexo transaction type or a separate message format.

To identify a transaction as Gasóleo Bonificado, send the following exact value in the card environment:

<CardBrnd>GASOLEO_BONIFICADO</CardBrnd>

The value is case-sensitive. Keep the uppercase spelling and underscore exactly as shown.

Supported nexo versions and messages

The CardBrnd value can be used with the standard card flows in nexo versions 5 and 6. The examples in this document use nexo version 6.

Availability of an individual transaction type depends on the merchant and terminal configuration.

Request field

For an Acceptor Authorisation Request, use this path:

Document/AccptrAuthstnReq/AuthstnReq/Envt/Card/CardBrnd

c = conditional: include this field when the transaction must be identified explicitly as Gasóleo Bonificado.

All other fields follow the normal nexo rules for the selected transaction. In particular, continue to use the standard values for Hdr/MsgFctn, Tx/TxCaptr, Tx/TxTp, amount, currency, card-entry mode, and cardholder verification. Do not change those fields solely because the card brand is Gasóleo Bonificado.

Card example

Add CardBrnd to the normal Envt/Card block. The following fragment uses placeholder card data and is not a complete request:

<Envt>
  <!-- Acquirer, merchant and POI data -->
  <POI>
    <!-- POI identification and capabilities -->
  </POI>
  <Card>
    <PrtctdCardData>
      <!-- Protected card data required by your integration -->
    </PrtctdCardData>
    <CardBrnd>GASOLEO_BONIFICADO</CardBrnd>
  </Card>
  <Crdhldr>
    <!-- Cardholder authentication or verification data, when required -->
  </Crdhldr>
</Envt>

Use the card-data protection method agreed for the production integration. Do not send or log clear card data unless the environment and integration explicitly permit it.

Online Sale example

The following fragment shows the Gasóleo Bonificado addition to a standard nexo version 6 online Sale.
Standard header, environment, context, security, and card-data elements are abbreviated for readability.

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:caaa.001.001.06">
  <AccptrAuthstnReq>
    <Hdr>
      <MsgFctn>FAUQ</MsgFctn>
      <PrtcolVrsn>6.0</PrtcolVrsn>
      <!-- Other required header fields -->
    </Hdr>
    <AuthstnReq>
      <Envt>
        <!-- Acquirer, merchant and POI data -->
        <Card>
          <PrtctdCardData>
            <!-- Protected card data -->
          </PrtctdCardData>
          <CardBrnd>GASOLEO_BONIFICADO</CardBrnd>
        </Card>
      </Envt>
      <Cntxt>
        <!-- Required payment context, including card-data entry mode -->
      </Cntxt>
      <Tx>
        <TxCaptr>true</TxCaptr>
        <TxTp>CRDP</TxTp>
        <MrchntCtgyCd>5541</MrchntCtgyCd>
        <TxId>
          <TxDtTm>2026-08-25T10:15:30+02:00</TxDtTm>
          <TxRef>GB-000001</TxRef>
        </TxId>
        <TxDtls>
          <Ccy>EUR</Ccy>
          <TtlAmt>75.00</TtlAmt>
        </TxDtls>
      </Tx>
    </AuthstnReq>
  </AccptrAuthstnReq>
</Document>

The merchant category code in the example is illustrative. Send the code configured and applicable to the merchant location.

Response handling

When the resolved brand is available, the Gateway returns it in the response card environment. For an Acceptor Authorisation Response, use this path:

Document/AccptrAuthstnRspn/AuthstnRspn/Envt/Card/CardBrnd

Example:

<Envt>
  <Card>
    <MskdPAN>************1234</MskdPAN>
    <CardBrnd>GASOLEO_BONIFICADO</CardBrnd>
  </Card>
</Envt>

CardBrnd confirms the resolved card brand. It does not indicate whether the transaction was approved. Always evaluate the standard transaction result, for example:

AuthstnRspn/TxRspn/AuthstnRslt/RspnToAuthstn/Rspn

Typical result values are APPR and DECL.

Follow-on transactions

For a completion, return, cancellation, or other linked transaction:

• identify the original transaction using the standard nexo reference fields required by that flow;
• copy GASOLEO_BONIFICADO into Envt/Card/CardBrnd when card data or a card block is supplied; and
• keep the amount, currency, and original-transaction references consistent with the selected flow.

The Gateway can resolve the brand from a correctly linked original transaction. Supplying the same brand value consistently is recommended when the message contains Envt/Card, especially for an unlinked credit where no original transaction is available.