the present invention provides an advantageous solution for enabling buyers to push credit payments as a buyer initiated transactions such that the credit card infrastructure can be used in part to make cash payments to vendors or merchants . looking first to the fig1 b ( prior art ), a block diagram is provided for a typical environment 150 for a merchant initiated credit card transaction . the card holder 152 communicates with an issuing bank 154 to receive credit and one or more credit cards for use in credit card transactions . line 166 represents an interaction between the card holder 152 and a merchant 160 where a credit card is used to make a purchase of goods and / or services . this interaction is a merchant initiated credit transaction because the merchant 160 performs a “ swiping ” event , as discussed above , in which the merchant 160 obtains the card holder &# 39 ; s credit card information and places the transaction into the credit card system . rather than collect payment directly , the merchant 160 will often use an acquirer 158 , which will receive the rights to the merchant &# 39 ; s receipts 162 in return for payment 164 of some percentage of the value of the receipts ( x % receipts ). these percentages are agreed upon between the merchant 160 and the acquirer 158 and are often between 97 . 5 % to 98 %. once this acquirer transaction has occurred , the acquirer 158 then works through the card processor 156 and the issuing bank 154 to receive funds from the card holder &# 39 ; s accounts . fig1 a provides a block diagram for an environment 100 for a buyer initiated credit payment according to the present invention . similar to fig1 b ( prior art ) the card holder 152 obtains credit from an issuing bank 154 and has cash accounts residing at the issuing bank 154 , such as a cash management account . the credit can be used , for example , to make credit card transactions . the cash account , however , is what is typically used to satisfy accounts payable operations . as contemplated by the present invention , these accounts can also to allow the card holder 152 to initiate credit payments as buyer initiated transactions . as indicated by line 102 in fig1 a , the card holder 152 can generate a buyer initiated credit transaction , for example , by communicating appropriate instructions to the acquirer 158 . the acquirer 158 can then treat the transaction as a soft - credit or pseudo - credit transaction , making payment 164 to the merchant 160 and working with card processor 156 and the issuing bank 154 to receive funds from the card holder &# 39 ; s accounts . although the buyer initiated credit transaction could be inserted into the system in another manner , the use of the acquirer 158 is advantageous because the acquirer 158 already performs a similar function in traditional merchant initiated credit card transactions . the significant and advantageous difference provided by the present invention is that the card holder 152 provides the payment instructions directly to the acquirer 158 , as represented by line 102 , and that these payment instructions are processed by the acquirer 158 as a pseudo - credit transaction rather than the payment being initiated by the merchant through a prior credit card transaction . it is noted that for the present invention , the card holder could simply be a buyer that has an account at a bank 154 and that it is not necessary for the buyer to also have credit at the bank . it is also noted that entities other than credit card transaction acquirers could be used to implement the present invention . as indicated above , however , because acquirers already have significant database information about merchants through their credit card settlement activities , acquirers make particularly good entities to use for buyer initiated payments in the form of soft or mimicked credit transactions . as indicated in fig1 a , the buyer initiated credit transaction 102 can also be controlled and managed through a purchasing management system 152 . a purchasing management system that in part facilitates the use and management of payment cards for corporate purchasing needs is described with respect to u . s . patent application ser . no . 10 / 083 , 445 (&# 39 ; 445 application ) which was filed oct . 19 , 2001 , and is entitled “ dynamic payment cards and related management systems and associated methods ,” the entire text and all contents for which is hereby expressly incorporated by reference in their entirety . the buyer initiated credit payment of the present invention can be included as an additional capability of such a purchasing management system . for example , a corporate accounting department could use the purchasing management system and the buyer initiated credit payment to accomplish cash payments for accounts payable operations where these payments would have been previously handled through a less efficient mechanism such as through paper check processes . as such , the resulting purchasing management system would not only allow for management of payment cards used by the company , but would also allow pushed credit transactions to be used for direct cash payments to vendors and merchants . in addition , the purchasing management system 152 can utilize a database that includes merchant profile information , such as the merchant &# 39 ; s preferences around the maximum amount the merchant is willing to take on a card before requiring a cash transaction . the purchasing management system 152 can further be configured to consult the merchant profile to determine whether a credit transaction or a debit transaction was the appropriate payment vehicle to communicate to the bank 154 and the acquirer 158 . if the transaction is to be a credit transaction , then the acquirer 158 processes the payment instructions as a pseudo - credit transaction , as discussed above . if the transaction is to be a debit / cash transaction , then the purchasing management system 152 can control and manage an automated funds transfer , such as through an automated clearing house payments ( ach ), to provide money from the buyer &# 39 ; s cash accounts to the acquirer 158 for payment to the merchant 160 . fig2 provides an example flow diagram 200 for a buyer initiated payment , according to the present invention . block 202 represents the beginning of a buyer initiated payment . in block 204 , payment instructions would be provided by the buyer that define the transaction desired by the buyer . for example , instructions could include description of the goods or services , the merchant identification , and a choice of paying with cash or credit . if a credit transaction is selected , a credit card number or identifier could be included as well . information about merchants and details of their payment options or other details can be stored in a merchant directory 206 . this merchant directory can be used by the buyer in determining what instructions to include in the desired transaction . for example , an accounting employee can look at the merchant directory 206 to determine what forms of payment are accepted by a particular merchant and to help determine the appropriate payment instructions for a particular merchant . if a cash transaction is selected , as indicated by block 208 , then two processing paths are entered . looking to the customer / buyer account in block 216 , an intra - bank transfer from the customer / buyer account ( such as a cash management account ) can be moved to a bank holding account . as represented in block 218 , periodic electronic payments , such as automated clearing house payments ( ach ), can occur from the bank holding account to the acquirer to settle the pseudo - credit transactions . flow then proceeds to block 210 from block 218 or directly from block 208 to block 210 should a credit payment be selected . in block 210 , payment instructions are communicated to and received by an acquirer . these communications are preferably electronic communications , such as electronic communications from a purchasing management system . in block 212 , the acquirer then can generate a software - based card transaction for the particular a merchant , if a credit payment has been selected , and can use this pseudo - credit transaction information for settlement of the transaction . it is noted that the transaction could also be a debit payment applied to the merchant , if a cash payment has been selected . in block 214 , the merchant receives payment or a debit from the acquirer . fig3 is a flow diagram 300 for an environment that includes buyer initiated credit payments as an option along with other transaction activities . block 302 represent a discretionary payment process where a buyer has discretionary purchasing authority , such as through a payment card that has been allocated some purchasing power . block 304 represents a merchant initiated card payment where the buyer has presented a payment card to a merchant to make a purchase . block 306 represents a credit payment made by a purchaser , for example , to the issuing bank . block 308 represents post - purchase review , accounting and reconciliation related to the purchase . finally , block 310 represents export of accounting information to a desired accounting program . block 312 represents a purchaser who is attempting to obtain approval for a purchase , for example , through an electronic user interface ( ui ) or custom import operation . block 314 represents a pre - purchase approval process through which the requested transaction gets approved or rejected . once approved , the transaction can proceed along to block 304 where a merchant initiates a card payment transaction , as discussed above . it is noted that the &# 39 ; 445 application discussed above provides a purchasing management system that advantageously provides dynamic management of payment cards and discloses example purchasing flows that are similar to those in fig3 flowing from block 302 and / or block 312 to block 304 . the present invention , as discussed above , adds a further advantageous feature of buyer initiated payments 320 that use existing credit transaction infrastructure . looking to block 314 , it is noted that purchase flow can proceed to block 318 in addition to block 304 . in block 318 , pre - payment accounting is accomplished with respect to the approved purchase request . as shown , block 318 may also be reached from block 316 , which represents accounts payable ( a / p ) operations . these a / p operations and information , for example , can be provided electronically through an user interface ( ui ) or custom import operation . once pre - payment accounting has been completed , a buyer credit payment can be initiated , as represented by block 320 . this buyer initiated credit payment can be implemented , as discussed above , by sending appropriate payment instructions to an acquirer who then processes the buyer initiated payments as a software - based or pseudo - credit transaction . in addition , debit or cash payments may also be buyer initiated in block 320 . as such , a merchant can then receive an a / p credit payment , as indicated by block 322 , or an a / p debit payment as indicated by block 324 through settlement processes performed by an acquirer , as discussed above . by taking advantage of the nature of existing credit card transaction infrastructures , therefore , the present invention allows for a buyer to initiate or push a credit payment by sending payment instructions directly to acquirers . acquirers can then treat the transaction as they would treat a credit card transaction , making a payment to the merchant according to the terms set by the buyer and obtaining payment from the buyer &# 39 ; s bank accounts . further modifications and alternative embodiments of this invention will be apparent to those skilled in the art in view of this description . it will be recognized , therefore , that the present invention is not limited by these example arrangements . accordingly , this description is to be construed as illustrative only and is for the purpose of teaching those skilled in the art the manner of carrying out the invention . it is to be understood that the forms of the invention herein shown and described are to be taken as the presently preferred embodiments . various changes may be made in the implementations and architectures described herein . for example , equivalent elements may be substituted for those illustrated and described herein , and certain features of the invention may be utilized independently of the use of other features , all as would be apparent to one skilled in the art after having the benefit of this description of the invention .