Scenario 18: Real-Time Funding

<< Back to the index

For more RTF scenarios, see Real-Time Funding Transaction Examples.

A company has set up a real-time funding (RTF) source account and has issued a number of RTF spending accounts that are associated with it. An RTF spending cardholder makes a $45 purchase at a retail outlet. The following are true:

  1. The RTF funding account (PRN: 333333333333) has a $1000 available balance.
  2. The RTF spending account (PRN: 777777777777) has a $0 available balance.
  3. The network is Mastercard Debit Switch (Maestro).

Sequence of events

Events in the same step have the same timestamp.

  1. Mastercard sends an authorization request for –45.00.
  2. Galileo moves 45.00 from the RTF funding account to the RTF spending account. The RTF funding account now has an available balance of 955.00 and the RTF spending account has an available balance of 45.00. Galileo approves the authorization request and puts a 45.00 hold on the RTF spending account. The RTF spending account now has an available balance of 0.00. Galileo sends the BAUT: auth event message.
  3. Two days later, Maestro sends a settlement batch file with the –45.00 transaction.
  4. Galileo backs out the 45.00 hold and posts –45.00 to the RTF spending account. The RTF spending account still has an available balance of 0.00 and the RTF funding account still has a 955.00 balance. Galileo sends the SETL: setl event message.

Transactions

These tables show how the transactions are represented by various Galileo systems. For an explanation of the trans_code field, see Classifying transactions in the About Transactions guide.

Auth API

auth_typetransaction_typetrans_amountauth_idoriginal_idavailable_fundstimestamp
AuthAuth45.00330004520210414:141529MST

Authorization/Settlement Events webhooks

msg_idtypeamountauth_idoriginal_auth_idopen_to_buytimestamp
BAUTauth453300002021-04-14 14:15:29 MST
SETLsetl453300002021-04-16 06:16:30 MST

Authorized Transactions RDF

TRANSACTION AMOUNTAUTHORIZATION CODETRANSACTION CODEREVERSAL IDPRNTRANSACTION DATE/TIME
45.00-3300507777777777772021-04-14 14:15:29

Posted Transactions RDF

TRANSACTION AMOUNTAUTHORIZATION CODETRANSACTION CODE/TYPESOURCE IDPRNTRANSACTION DATE/TIMEPOST DATE
45.00-4477ADFY44773333333333332021-04-14 14:15:292021-04-14 14:15:29
45.00+4478ADSY44787777777777772021-04-14 14:15:292021-04-14 14:15:29
45.00-3300SDA33007777777777772021-04-1414:15:292021-04-16 06:16:30

Get Authorization History response

This endpoint returns only transactions that have not settled or expired. These transactions are also returned by Get Account Overview. This endpoint does not return the RTF adjustments.

amtauth_idoriginal_auth_idtypelocal_amttimestamp
-453300050000000045002021-04-14 14:15:29

Get Transaction History response

This endpoint returns only settled transactions. These transactions are also returned by Get Account Overview. This endpoint does not return the RTF adjustments.

amtsource_idoriginal_auth_idtrans_codeauth_tspost_ts
-4533000SDA2021-04-14 14:15:292021-04-16 06:16:30

Get All Transaction History response

This endpoint returns the same transactions as the All Transactions screen of the CST. This is the response when accountNo is the RTF spending account.

amtauth_idprior_idtrans_codesource_idcalculated_balancecredit_indauth_tspost_ts
453300NoneADSY447845None2021-04-14 14:15:292021-04-14 14:15:29
-4533000DBA33000N2021-04-14 14:15:292021-04-14 14:15:29
45NoneNoneBDA330045NoneNone2021-04-16 06:16:30
-4533000SDA33000N2021-04-14 14:15:292021-04-16 06:16:30