Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feat: Add support for industry practice transaction indicators #43

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

mustafa-ixo
Copy link
Collaborator

@mustafa-ixo mustafa-ixo commented Jul 17, 2024

  • Currently, we support the transaction indicator “CARDONFILE-MERCHANT-INITIATED” for arbitrary, unscheduled, merchant initiated transactions (“COF MIT” or simply “MIT” in short).

  • For certain business cases, schemes have introduced sub-types of a MIT transaction (Industry Practice MIT). Industry practice MITs may be performed with credentials that the Merchant does not store permanently on file, but only temporarily retains for purposes of completing the purchase.

  • The ultimate goal is to add general support within our processing framework for sending these indicators (milestone 1) and subsequently pass-on these indicators accordingly to individual adapters where supported (milestone 2; out of scope). However, two POC adapters are in-scope for milestone 1, see Assumptions section.

  • The new indicators and their use cases are the following:

    • Partial shipment” occurs when items that were out of stock when originally ordered in a CIT are later shipped and billed separately by the merchant as an MIT.
    • Related/delayed charge” occurs when the merchant submits an MIT to bill the cardholder for additional items or fees associated with an initial CIT, in accordance with the original transaction terms.
    • No-show” is a fee billed by a merchant in accordance with the merchant’s guaranteed reservation service policy, when the cardholder fails to cancel a reservation within the time frame disclosed at the time of the booking.
    • Resubmission” occurs when the original CIT authorization request was declined by the issuer for a reason that does not preclude the merchant from re-submitting the request after a reasonable period (for example, in 24 hours).
    • That is, merchants may use this indicator for retrying a previously failed charge for reasons like “insufficient funds” or a temporary technical error.
  • Tello

  • RFC

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant