Swipe flag scenarios

This article provides examples of swipe flag scenarios.

This documentation explains how LoanPro’s swipe flags handle various transaction authorization scenarios. Swipe Flag handling is a necessity for users implementing a Bring Your Own Issuer (BYOI) integration with LoanPro’s card platform. For more information on swipes and the swipe flags, see our swipes documentation.

Scenario #1

Flag:	Value:	Authorization checks:	Swipe event(s):	Swipe event result:	Scenario description:
issuer-decline	false	Card status is active Available balance is sufficient Swipe restrictions do not apply Spend limit is not exceeded	`authorization`	Authorized Account = {{authorized amount of the swipe}}	This scenario is used when a transaction authorization request is made with a Dual Message System (DMS). If the authorization request is DMS, it will be indicated within the request for authorization. This type of authorization request occurs when a transaction is either categorized as an online purchase or ecommerce. However, this is not always the case; for example, Point of Sale (POS) transactions at a payment terminal may also be DMS transactions. This type of authorization request may also be referred to as a "card not present" authorization request. In this case, the swipe will be created and all authorization checks will occur. An `authorization` type swipe event will be the first and only event created on the swipe. The event will show the result of the authorization checks
authorization-advice	false
preauthorization	false
force-clearing	false
cash-advance	false
credit-authorization	false
sma	false

Scenario #2

Flag:	Value:	Authorization checks:	Swipe event(s):	Swipe event result:	Scenario description:
issuer-decline	true	N/A	`authorization`	Declined: Issuer Decline	The intention of this flag is to log a declined swipe for a dual message system (DMS) authorization request that was declined by the card’s issuing processor before reaching LoanPro to be authorized. In this case, the swipe will be created and no authorization checks will occur because the `issuer-decline` flag is set to true, and a normal `authorization` type swipe event will be the first event created on the swipe for the amount that was specified as the swipe amount. The authorization type swipe event will be marked as "Declined: Issuer Decline" and no funds will be authorized.
authorization-advice	false
preauthorization	false
force-clearing	false
cash-advance	false
credit-authorization	false
sma	false

Scenario #3

Flag:	Value:	Authorization checks:	Swipe event(s):	Swipe event result:	Scenario description:
issuer-decline	false	N/A	`authorization-advice`	Authorized Amount = {{authorized amount of the swipe}}	The intention of this flag is to log an authorized swipe for DMS authorization requests that have been authorized by Stand-In Processing (STIP) from the network or issuing processor of the card on LoanPro's behalf. LoanPro will receive “advice to inform” for the authorized transaction, and it cannot be declined because it has already been approved by the network or issuing processor. In this case, the swipe will be created and no authorization checks will occur because the `authorization-advice` flag is set to true, and an `authorization-advice` type swipe event will be the first event created on the swipe for the amount that was specified as the swipe amount The authorization-advice type swipe event amount is set as the Authorized Amount of the swipe.
authorization-advice	true
preauthorization	false
force-clearing	false
cash-advance	false
credit-authorization	false
sma	false

Scenario #4

Flag:	Value:	Authorization checks:	Swipe event(s):	Swipe event result:	Scenario description:
issuer-decline	false	Card status is active Available balance is sufficient Swipe restrictions do not apply Spend limit is not exceeded	`preauthorization`	Authorized Amount = {{authorized amount of the swipe}}	This flag will be used when a request for authorization is an estimate or max amount to be authorized. These types of authorizations expire quicker than others and are usually followed up with an `authorization-advice` type swipe event to update the Authorized Amount of the swipe to the actual amount requested by the merchant. In this case, the swipe will be created and all authorization checks will run. A `preauthorization` type swipe event will be the first event created on the swipe and it will show the result of the authorization checks.
authorization-advice	false
preauthorization	true
force-clearing	false
cash-advance	false
credit-authorization	false
sma	false

Scenario #5

Flag:	Value:	Authorization checks:	Swipe event(s):	Swipe event result:	Scenario description:
issuer-decline	false	N/A	`forced-clearing`	Cleared Amount = {{cleared amount of the swipe}}	This flag will be used when a clearing message has been recieved with no prior authorization being requestd for the transaction. This is bad practice by the payment processor of the merchant and will not commonly occur, but it is a possibility that is accounted for. Most issuing processors will mark a transaction as a "forced post" or something similar to indicate that the funds were not authorized but are now being cleared. In this case, the swipe will be created and no authorization checks will occur because the `force-clearing` flag is set to true. A `force-clearing` type swipe event will be the first event created on the swipe to indicate that this swipe was cleared without any prior authorization being requested.
authorization-advice	false
preauthorization	false
force-clearing	true
cash-advance	false
credit-authorization	false
sma	false

Scenario #6

Flag:	Value:	Authorization checks:	Swipe event(s):	Swipe event result:	Scenario description:
issuer-decline	false	Card status is active Available advance balance is sufficient Swipe restrictions do not apply Spend limit is not exceeded	`authorization`	Authorized Amount = {{authorized amount of the swipe}}	This flag will rarely be set to `true` by itself. Usually this flag will be checked along with the `sma` flag because money is being authorized and cleared at the same time during most cash advance transactions. In this case, the swipe will be created and authorization checks will occur-taking into account the `cash advance` flag being set to `true`-meaning that avilable advance balance will be used instead of the available balance to verify the availability of funds for the transaction. An `authorization` type swipe event will be the first event created on the swipe, and it will show the result of the authorization checks.
authorization-advice	false
preauthorization	false
force-clearing	false
cash-advance	true
credit-authorization	false
sma	false

Scenario #7

Flag:	Value:	Authorization checks:	Swipe event(s):	Swipe event result:	Scenario description:
issuer-decline	false	Card status is active	`credit-authorization`	Authorized Credit Amount = {{authorized credit amount of the swipe}}	This flag will be used to indicate that money is being authorized to be given as a credit on the card through a DMS credit authorization. A use case for this scenario could involve a cardholder returning an item to a merchant. The merchant will then return the funds used to purchase the item back to the cardholder as a credit on the card. A clearing message will later be recieved to indicate that the credit has cleared for which a Clearing type swipe event will be created. In this case, the swipe will be created and the only authorization check that will occur on the card will be to verify that the card is in the "Active" status. A `credit-authorization` type swipe event will be the first event created on the swipe and it will show the result of the credit authorization check for card status.
authorization-advice	false
preauthorization	false
force-clearing	false
cash-advance	false
credit-authorization	true
sma	false

Scenario #8

Flag:	Value:	Authorization checks:	Swipe event(s):	Swipe event result:	Scenario description:
issuer-decline	false	Card status is active Available balance is sufficient Swipe restrictions do not apply Spend limit is not exceeded	`authorization`	Authorized Amount = {{authorized amount of the swipe}}	This flag will be used when a transaction is requested to be authorized with a Single Message System (SMS). If the authorization request is SMS, it will be indicated within the request for authorization This type of authorization request will occur when a transaction is considered Point-of-Sale (POS) and is made at a payment terminal. This type of authorization request could also be referred to as a "Full Financial" authorization request. In this case, the swipe will be created and all authorization checks will occur. An `authorization` type swipe event will be the first event created on the swipe, and it will show the result of the authorization checks if the swipe was approved by the authorization checks, then LoanPro will automatically add a `clearing` type swipe event to the swipe for the amount that was authorized.
authorization-advice	false		`authorization`	Authorized Amount = {{authorized amount of the swipe}}
preauthorization	false		`clearing`	Cleared Amount = {{cleared amount of the swipe}}
force-clearing	false		`clearing`	Cleared Amount = {{cleared amount of the swipe}}
cash-advance	false
credit-authorization	false
sma	true

Scenario #9

Flag:	Value:	Authorization checks:	Swipe event(s):	Swipe event result:	Scenario description:
issuer-decline	true	N/A	`preauthorization`	Declined: Issuer Decline	The intention of this flag set is to log a declined sipe for DMS preauthorization requests that were declined by the issuing processor of the card before ever reaching LoanPro to be authorized. In this case, the swipe will be created, no authorization checks will occur due to the `issuer-decline` flag being set to true, and a `preauthorization` type swipe event will be the first event created on the swipe. The `preauthorization` type swipe event will be marked as "Declined: Issuer Decline" and no funds will be authorized.
authorization-advice	false
preauthorization	true
force-clearing	false
cash-advance	false
credit-authorization	false
sma	false

Scenario #10

Flag:	Value:	Authorization checks:	Swipe event(s):	Swipe event result:	Scenario description:
issuer-decline	true	N/A	`authorization`	Declined: Issuer Decline	The intention of this flag set is to log a declined swipe for DMS cash advance authorization requests that were declined by the issuing processor of the card before ever reaching LoanPro to be authorized In this case, the swipe will be created, no authorization checks will occur due to the `issuer-decline` flag being set to true, and a normal `authorization` type swipe event will be the first event created on the swipe. The `authorization` type swipe event will be marked as "Declined: Issuer Decline" and no funds will be authorized.
authorization-advice	false
preauthorization	false
force-clearing	false
cash-advance	true
credit-authorization	false
sma	false

Scenario #11

Flag:	Value:	Authorization checks:	Swipe event(s):	Swipe event result:	Scenario description:
issuer-decline	true	N/A	`credit-authorization`	Declined: Issuer Decline	The intention of this flag set is to log a declined swipe for DMS credit authorization requests that was declined by the issuing processor of the card before ever reaching LoanPro to be authorized. In this case, the swipe will be created, no authorization checks will occur due to the `issuer-decline` flag being set to true, and a `credit-authorization` type swipe event will be the first event created on the swipe. The `credit-authorization` type swipe event will be marked as "Declined: Issuer Decline" and no funds will be authorized as credit.
authorization-advice	false
preauthorization	false
force-clearing	false
cash-advance	false
credit-authorization	true
sma	false

Scenario #12

Flag:	Value:	Authorization checks:	Swipe event(s):	Swipe event result:	Scenario description:
issuer-decline	true	N/A	`authorization`	Declined: Issuer Decline	The intention of this flag set is to log a declined swipe for SMS authorization requests that were declined by the issuing processor of the card before ever reaching LoanPro to be authorized. In this case, the swipe will be created, no authorization checks will occur due to the `issuer-decline` flag being set to true, and a normal `authorization` type swipe event will be the first event created on the swipe. The `issuer-decline` flag overrides the `sma` flag regarding which swipe events will be added to the swipe when it is created.
authorization-advice	false
preauthorization	false
force-clearing	false
cash-advance	false
credit-authorization	false
sma	true

Scenario #13

Flag:	Value:	Authorization checks:	Swipe event(s):	Swipe event result:	Scenario description:
issuer-decline	false	N/A	`authorization-advice`	Authorized Amount = {{authorized amount of the swipe}}	The intention of this flag set is to log an authorized swipe for the DMS cash advance requests that have been authorized by the STIP from the network or issuing processor on LoanPro's behalf. LoanPro will recieve "advice to inform" for the authorized transaction, and it cannot be declined because it has already been approved by the network or issuing processor. In this case, the swipe will be created, no authorization checks will occur due to the `authorization-advice` flag being set to true, and an `authorization-advice` type swipe event will be the first event created on the swipe.
authorization-advice	true
preauthorization	false
force-clearing	false
cash-advance	true
credit-authorization	false
sma	false

Scenario #14

Flag:	Value:	Authorization checks:	Swipe event(s):	Swipe event result:	Scenario description:
issuer-decline	false	N/A	`authorization-advice`	Authorized Amount = {{authorized amount of the swipe}}	The intention of this flag set is to log an authorized swipe for DMS cash advance requests that have been authorized by STIP from the network or issuing processor on LoanPro's behalf. LoanPro will recieve "advice to inform" for the authorized transaction, and it cannot be declined because it has already been approved by the network or issuing processor. In this case, the swipe will be created, no authorization checks will occur due to the `authorization-advice` flag being set to true, and an `authorization-advice` type swipe event will be the first event created on the swipe.
authorization-advice	true		`authorization-advice`	Authorized Amount = {{authorized amount of the swipe}}
preauthorization	false		`clearing`	Cleared Amount = {{cleared amount of the swipe}}
force-clearing	false		`clearing`	Cleared Amount = {{cleared amount of the swipe}}
cash-advance	false
credit-authorization	false
sma	true

Scenario #15

Flag:	Value:	Authorization checks:	Swipe event(s):	Swipe event result:	Scenario description:
issuer-decline	false	N/A	`credit-authorization`	Approved Authorization Advice, Authorized Credit Amount = {{authorized credit amount of the swipe}}	The intention of this flag set is to log an authorized credit for DMS credit authorization requests that have been authorized by STIP from the network or issuing processor of the card on LoanPro's behalf. LoanPro will recieve "advice to inform" for the authorized credit, and it cannot be declined because it has already been approved by the network or issuing processor. A clearing message will be sent to clear the credit that has been authorized. In this case, no authorization checks will occur. A `credit-authorization` type swipe event will be the first event created on the swipe. The `credit-authorization` event will have a result of "Approved Authorization Advice, Authorized Credit Amount = {authorized credit amount of the swipe}".
authorization-advice	true
preauthorization	false
force-clearing	false
cash-advance	false
credit-authorization	true
sma	false

Scenario #16

Flag:	Value:	Authorization checks:	Swipe event(s):	Swipe event result:	Scenario description:
issuer-decline	false	Card status is active Available balance is sufficient Swipe restrictions do not apply Spend limit is not exceeded	`preauthorization`	Authorized Amount = {{authorized amount of the swipe}}	The intention of this flag set is to authorize a swipe for DMS preauthorization cash advance requests. This scenario will nearly never occur because a preauthorization request usually indicates that the requested amount is an estimated purchase price. The requested amount will never be an estimate in the case of a cash advance. However, the tools here acount for the scenario if it were to arise. In this case, the swipe will be created, an authorization check will occur while acknowledging the `cash-advance` flag being set to true. A `preauthorization` type swipe event will be the first event created on the swipe, and it will show the result of the authorization checks.
authorization-advice	false
preauthorization	true
force-clearing	false
cash-advance	true
credit-authorization	false
sma	false

Scenario #17

Flag:	Value:	Authorization checks:	Swipe event(s):	Swipe event result:	Scenario description:
issuer-decline	false	N/A	`forced-clearing`	Cleared Amount = {{cleared amount of the swipe}}	This flag set will be used when a clearing message has been recieved with no prior authorization request for the transaction in addition to the clearing message having been marked as a cash advance. This is bad practice by the payment processor of the merchant and will not commonly occur, but it is a possibility that is accounted for. Most issuing processors will mark a transaction as a "forced post" or something similar to indicate that the funds were not authorized but are now being cleared. In this case, the swipe will be created, no authorization checks will occur due to the `force-clearing` flag being set to true, and a `forced-clearing` type swipe event will be the first event created on the swipe. The `cash-advance` flag does not matter because no authorization checks were run on the swipe. However, it will likely matter for interest calculation depending on how the card has been set up.
authorization-advice	false
preauthorization	false
force-clearing	true
cash-advance	true
credit-authorization	false
sma	false

Scenario #18

Flag:	Value:	Authorization checks:	Swipe event(s):	Swipe event result:	Scenario description:
issuer-decline	false	N/A	`credit-authorization`	Approved Authorization Advice, Authorized Credit Amount = {{authorized credit amount of the swipe}}	This flag will be used when a clearing message has been recieved with no prior authorization request for the transaction in addition to the cardholder. Most issuing processors will mark a transaction as a "forced post" or something similar to indicate that the funds were not authorized but they are now being cleared to be returned to the card. In this case, no authorization checks occur on the swipe. A `credit-authorization` type swipe event will be the first event created on the swipe. The `credit-authorization` event will have a result of "Approved Forced Clearing, Authorized Credit Amount = {Amount of the swipe}" then a `forced-clearing` type swipe event will automatically be added to the swipe for the amount that was specified in the swipe.
authorization-advice	false		`credit-authorization`
preauthorization	false		`forced-clearing`	Cleared Amount = {{cleared amount of the swipe}}
force-clearing	true		`forced-clearing`	Cleared Amount = {{cleared amount of the swipe}}
cash-advance	false
credit-authorization	true
sma	false

Scenario #19

Flag:	Value:	Authorization checks:	Swipe event(s):	Swipe event result:	Scenario description:
issuer-decline	false	Card status is active Available balance is sufficient Swipe restrictions do no apply Spend limit is not exceeded	`authorization`	Authorized Amount = {{authorized amount of the swipe}}	The intention of this flag set is to authorize an SMS cash advance authorization request. If the authorization request is SMS, it will be indicated within the request for authorization. This type of authorization request (SMS) will be commonly used for cash advance authorization requests. This type of authorzation request may also be referred to as a "Full Financial" cash advance authorization request. In this case, the swipe will be created, authorization checks will occur while acknowledging the `cash-advance` flag being set to true. An `authorization` type swipe event will be the first event created on the swipe, and it will show the result of the authorization checks. If the swipe was apporved by the authorization check, then a `clearing` type swipe event will be automatically be added to the swipe by LoanPro for the amount that was authorized.
authorization-advice	false		`authorization`	Authorized Amount = {{authorized amount of the swipe}}
preauthorization	false		`clearing`	Cleared Amount = {{cleared amount of the swipe}}
force-clearing	false		`clearing`	Cleared Amount = {{cleared amount of the swipe}}
cash-advance	true
credit-authorization	false
sma	true

Scenario #20

Flag:	Value:	Authorization checks:	Swipe event(s):	Swipe event result:	Scenario description:
issuer-decline	false	Card status is active	`credit-authorization`	Authorized Credit Amount = {{authorized credit amount of the swipe}}	This flag set will be used to indicate that funds are being authorized to be given as a credit on the card through an SMS credit authorization. A use case for this scenario could involve a cardholder returning an item to a merchant. The merchant will then return the funds used to purchase the item back to the cardholder as a credit on the card. A clearing message will not be recieved to indicate that the credit has cleared because the credit authoration message is an SMS. In this case, the swipe will be created, authorization checks will occur to ensure the card exists and is in the "Active" status. A `credit-authorization` type swipe event will be the first event created on the swipe. If the return was approved by the card status check, then a `clearing` type swipe event will automatically be added to the swipe by LoanPro for the amount that was authorized because `sma` is set to true.
authorization-advice	false		`credit-authorization`
preauthorization	false		`clearing`	Cleared Amount = {{cleared amount of the swipe}}
force-clearing	false		`clearing`	Cleared Amount = {{cleared amount of the swipe}}
cash-advance	false
credit-authorization	true
sma	true

Scenario #21

Flag:	Value:	Authorization checks:	Swipe event(s):	Swipe event result:	Scenario description:
issuer-decline	true	N/A	`preauthorization`	Declined: Issuer Decline	The intention of this flag set is to log a declined swipe for DMS preauthorization cash advance requests that were declined by the issuing processor of the card before ever reaching LoanPro to be authorized. This scenario will rarely occur because a preauthorization request usually indicates that the requested amount is an estimated purchase price. The requested amount will never be an estimate in the case of a cash advance. However, the tools here acount for the scenario if it were to arise. In this case, the swipe will be created, no authorization checks will occur due to the `issuer-decline` flag being set to true, and a `preauthorization` type swipe event will be the first event created on the swipe. The `preauthorization` type swipe event will be marked as "Declined: Issuer Decline" an no funds will be authorized.
authorization-advice	false
preauthorization	true
force-clearing	false
cash-advance	true
credit-authorization	false
sma	false

Scenario #22

Flag:	Value:	Authorization checks:	Swipe event(s):	Swipe event result:	Scenario description:
issuer-decline	true	N/A	`authorization`	Declined: Issuer Decline	The intention of this flag set is to log a declined swipe for SMS cash advance authorization requests that were declined by the issuing processor of the card before ever reaching LoanPro to be authorized. This is the most likely scenario to occur if a cash advance authorization request is declined by STIP. In this case, the swipe will be created, no authorization checks will occur due to the `issuer-decline` flag being set to true, and a normal `authorization` type swipe event will be the first event created on the swipe. The `authorization` type swipe event will be marked as "Declined: Issuer Decline" and no funds will be authorized.
authorization-advice	false
preauthorization	false
force-clearing	false
cash-advance	true
credit-authorization	false
sma	true

Scenario #23

Flag:	Value:	Authorization checks:	Swipe event(s):	Swipe event result:	Scenario description:
issuer-decline	false	N/A	`authorization-advice`	Authorized Amount = [Authorized Amount of the swipe]	The intention of this flag set is to log an authorized swipe for SMS cash advance authorization requests that have been STIP authorized by the network or issuing processor of the card on LonaPro's behalf. In this scenario, LoanPro will recieve advice to inform of the authorized transaction and it cannot be declined because it has already been approved by the network or issuing processor. In this case, the swipe would be created, no authorization checks will occur due to `authorization-advice` flag is set to true, and an `authorization-advice` type swipe event will be the first event created on the swipe, followed by a `clearing` type swipe event for the amount of the `authorization-advice` because `SMA` flag is set to true. The Cash Advance flag does not matter for authorization, because no authorization checks will be run on the swipe. However, it will matter for interest calcluation depending on how the card has been set up.
authorization-advice	true		`authorization-advice`	Authorized Amount = [Authorized Amount of the swipe]
preauthorization	false		`clearing`	Cleared Amount = [Cleared Credit Amount of the swipe]
force-clearing	false		`clearing`	Cleared Amount = [Cleared Credit Amount of the swipe]
cash-advance	true
credit-authorization	false
sma	true

Scenario #24

Flag:	Value:	Authorization checks:	Swipe event(s):	Swipe event result:	Scenario description:
issuer-decline	false	N/A	`credit-authorization`	Approved Authorization Advice, Authorized Credit Amount = [Authorized Credit Amount of the swipe]	The intention of this flag set is to log an authorized credit for SMS credit authorization requests that have been STIP authorized by the network or issuing processor of the card on LoanPro's behalf. In this scenario, LoanPro will recieve advice to inform of the authorized credit and it cannot be declined because it has already been approved by the network or issuing processor. A clearing message will not be recieved to indicate that the credit has cleared because the credit authorization message is an SMS. In this case, the swipe will be created, no authorization checks will be run, a `credit-authorization` type swipe event will be the first event created on the swipe. Then a `clearing` type swipe event will be added to the swipe by LoanPro for the amount that was authorized because `SMA` flag is set to true. The credit authorization event will have a result "Approved Authorization Advice, Authorized Credit Amount = [Amount of the swipe]".
authorization-advice	true		`credit-authorization`
preauthorization	false		`credit-clearing`	Cleared Credit Amount = [Cleared Credit Amount of the swipe]
force-clearing	false		`credit-clearing`
cash-advance	false
credit-authorization	true
sma	true

Updated about 2 months ago