Quick payment / payment transaction protocol design process

Disclaimer: This article is a blogger original article, follow the CC 4.0 BY-SA copyright agreement, reproduced, please attach the original source link and this statement.
This link: https://blog.csdn.net/red_sheeps/article/details/79891555

background

(Angle station of this article is the third-party payment agencies)
before done fast transaction payment type, each bank out of the interfaces are different (including contracting and payments), and some need a complete (we call signed confirmation / payment confirmation), and some need two complete (+ sign to confirm the signing application / payment application + payment confirmation), while others need to complete three (signed application + SMS + contract signed confirmation / payment application + SMS + payment payment confirmation).

design

The following are a few pieces of said interaction and for the bank side.
In the contracting and payment process, certainly missed SMS verification, then how in the bank side of the open interfaces of different time SMS verification do it? Through a field smsSendStateto control the front-end system to send text messages through the payment institution sending or bank sent.
The field values are as follows:

The value meaning Explanation
1 Has been sent Bank logo has been sent, payment institutions no longer need to send side
2 To send Identify the banks need to send a text message via SMS transactions by payment institutions (the above-mentioned contract SMS / SMS payment) driver to send
3 Do not send Do not send text messages to identify the bank, by the payment agency to decide whether to send (usually pay agencies to send text messages and verification)

A complete

This situation is the subscription information / one-time payment information is sent to the bank to complete the agreement signing / debit action, this situation may be somewhat unsafe, we need to pay agencies to ensure the security of transactions.

flow chart

The following flow chart can be seen only once and banks to interact.

One interaction

Two complete

These two are application + confirm (generally signed application transaction can also be called authentication, signing confirm the transaction call sign), two points here, the reason why the transaction is a verification code to confirm the transaction by the bank to send ( bank sends codes), this model is the largest, most banks are in this way.

flow chart

The following flow chart can be seen, payment institutions and banks conducted two interactive

Two transactions

Three complete

Three cases of relatively small transactions, apply for a driving bank sends an SMS code once, eventually verify your bank to send text messages once again on the code, payment institutions and banks have a total of three times to interact.

flow chart

This mode is the most complex, there are three interactive.

Three Trading

to sum up

Either way is to pay for safety's sake, just the last end of the whole company system my department, for this difference has been shielded, the entire process is controlled by the field, open to the unity of three front-end trading system (application , SMS, confirmation), which will send the application and confirm that the two transactions, by returning the field of the application to decide whether to send text messages on the transaction, the entire process is generally quick to pay so be it.

Guess you like

Origin blog.csdn.net/red_sheeps/article/details/79891555