Documentation for a newer release is available. View Latest
Esta página no está disponible actualmente en Español. Si lo necesita, póngase en contacto con el servicio de asistencia de Icon (correo electrónico)

Handle Validate Scheme Rules - mmbId.story

Scenario: Handling validation of scheme rules invalid bic

Steps
When the Payment Service sends a 'Validate Scheme Rules Request' with values:
| getPayload().getContent().cdtTrfTxInf[0].<agent>.finInstnId.clrSysMmbId.mmbId  | <mmbid>                                |
| customBusinessData                                                             | supportingContext('flowType','<type>') |
Then the Payment Service receives a 'Validate Scheme Rules Response' with values:
| status                                | FAILURE                           |
| getPayload().getContent().reasonCode  | RC01                              |
| getPayload().getContent().description | MmbId value not allowed           |
| requestId                             | #ValidateSchemeRulesRequest.ipfId |
Tabla 1. Examples:
mmbid agent type

12345

instgAgt

CREDITOR

12345

instdAgt

DEBTOR

Example: {agent=instgAgt, type=CREDITOR, mmbid=12345}

com.iconsolutions.ipf.payments.csm.sic5.application.bdd.testfw.Steps.parseMeta(java.lang.String)

com.iconsolutions.ipf.payments.csm.sic5.application.bdd.testfw.Steps.parseLegacy(java.lang.String)

When the ｟Payment Service｠ sends a Validate Scheme Rules Request with values:
| getPayload().getContent().cdtTrfTxInf[0].｟instgAgt｠.finInstnId.clrSysMmbId.mmbId | ｟12345｠ |
| customBusinessData | supportingContext(flowType,｟CREDITOR｠) |

Then ｟the Payment Service｠ receives a Validate Scheme Rules Response with values:
| status | FAILURE |
| getPayload().getContent().reasonCode | RC01 |
| getPayload().getContent().description | MmbId value not allowed |
| requestId | #ValidateSchemeRulesRequest.ipfId |

com.iconsolutions.testfw.core.steps.BaseSteps.clearContext()

com.iconsolutions.testfw.core.steps.BaseSteps.clearContext()

com.iconsolutions.testfw.core.steps.BaseSteps.clearContext()

com.iconsolutions.testfw.core.steps.BaseSteps.clearContext()

com.iconsolutions.testfw.core.steps.BaseSteps.clearContext()

Example: {agent=instdAgt, type=DEBTOR, mmbid=12345}

com.iconsolutions.ipf.payments.csm.sic5.application.bdd.testfw.Steps.parseMeta(java.lang.String)

com.iconsolutions.ipf.payments.csm.sic5.application.bdd.testfw.Steps.parseLegacy(java.lang.String)

When the ｟Payment Service｠ sends a Validate Scheme Rules Request with values:
| getPayload().getContent().cdtTrfTxInf[0].｟instdAgt｠.finInstnId.clrSysMmbId.mmbId | ｟12345｠ |
| customBusinessData | supportingContext(flowType,｟DEBTOR｠) |

Then ｟the Payment Service｠ receives a Validate Scheme Rules Response with values:
| status | FAILURE |
| getPayload().getContent().reasonCode | RC01 |
| getPayload().getContent().description | MmbId value not allowed |
| requestId | #ValidateSchemeRulesRequest.ipfId |

com.iconsolutions.testfw.core.steps.BaseSteps.clearContext()

com.iconsolutions.testfw.core.steps.BaseSteps.clearContext()

com.iconsolutions.testfw.core.steps.BaseSteps.clearContext()

com.iconsolutions.testfw.core.steps.BaseSteps.clearContext()

com.iconsolutions.testfw.core.steps.BaseSteps.clearContext()