Setting batch numbers

I am using the C API to communicate between two instances of
POS
software and a single instance of the Monetra engine.

Is there a way to assign a sale transaction to a particular
batch at the
time that the transaction is sent to the Monetra engine? I
would like to
assign transactions from the different POS stations to
different batches
and issue independent settle requests (the customer
currently has two
card terminals that settle independently and likes it that
way).

It looks to me like the only way to do this is to issue a
setbatchnum
request before issuing the sale request. Without creating
different
subusers, this would cause a race condition. If there's a
way to
accomplish this without subusers, I'd like to.

Relatedly, setting new transactions to an old, settled batch
number and
then issuing another settle request for that batch seems to
only settle
the unsettled transactions without disturbing those already
settled, at
least with the Loopback processor. Other than confusing
reports, are
there reasons for not doing this?

John

_______________________________________________
Monetra-support mailing list
Monetra-supportlists.mainstreetsoftworks.com
http://lists.mainstreetsoftworks.com/mailma
n/listinfo/monetra-support

You should never do your own batch management.  Let Monetra
handle this.  You could get all sorts of out-of-balance
errors or failed settlements by trying the approach you
are stating.  The 'setbatchnum' request is strictly a tool
to help with resolving issues when working with your
processing
institution, definitely NOT something which should be used
daily (or even per-transaction!).  Do not expect that to
work in production.

If you need to manage transactions in separate batches,
contact
the company who provides your merchant account and get them
to assign you a separate terminal id.  You'd then add that
additional terminal id as a separate user/merchant account
in
Monetra, and have the respective POS's use the proper
username
password for each terminal id.

If you're just wanting that functionality for reporting
though,
you should probably just be using something like the
'stationid'
field of Monetra, and add that to your report query to see
what
that particular station had done.  That's the cheapest and
safest
way to handle the situation.

-Brad

John Tusciuk wrote:
> I am using the C API to communicate between two
instances of POS
> software and a single instance of the Monetra engine.
> 
> Is there a way to assign a sale transaction to a
particular batch at the
> time that the transaction is sent to the Monetra
engine? I would like to
> assign transactions from the different POS stations to
different batches
> and issue independent settle requests (the customer
currently has two
> card terminals that settle independently and likes it
that way).
> 
> It looks to me like the only way to do this is to issue
a setbatchnum
> request before issuing the sale request. Without
creating different
> subusers, this would cause a race condition. If there's
a way to
> accomplish this without subusers, I'd like to.
> 
> Relatedly, setting new transactions to an old, settled
batch number and
> then issuing another settle request for that batch
seems to only settle
> the unsettled transactions without disturbing those
already settled, at
> least with the Loopback processor. Other than confusing
reports, are
> there reasons for not doing this?
> 
> John
> 
> _______________________________________________
> Monetra-support mailing list
> Monetra-supportlists.mainstreetsoftworks.com
> http://lists.mainstreetsoftworks.com/mailma
n/listinfo/monetra-support
> 
_______________________________________________
Monetra-support mailing list
Monetra-supportlists.mainstreetsoftworks.com
http://lists.mainstreetsoftworks.com/mailma
n/listinfo/monetra-support

Thanks for clearing up my serious misconception!

John

Brad House wrote:
> You should never do your own batch management.  Let
Monetra
> handle this.  You could get all sorts of
out-of-balance
> errors or failed settlements by trying the approach
you
> are stating.  The 'setbatchnum' request is strictly a
tool
> to help with resolving issues when working with your
processing
> institution, definitely NOT something which should be
used
> daily (or even per-transaction!).  Do not expect that
to
> work in production.
> 
> If you need to manage transactions in separate batches,
contact
> the company who provides your merchant account and get
them
> to assign you a separate terminal id.  You'd then add
that
> additional terminal id as a separate user/merchant
account in
> Monetra, and have the respective POS's use the proper
username
> password for each terminal id.
> 
> If you're just wanting that functionality for reporting
though,
> you should probably just be using something like the
'stationid'
> field of Monetra, and add that to your report query to
see what
> that particular station had done.  That's the cheapest
and safest
> way to handle the situation.
> 
> -Brad
> 
> John Tusciuk wrote:
>> I am using the C API to communicate between two
instances of POS
>> software and a single instance of the Monetra
engine.
>>
>> Is there a way to assign a sale transaction to a
particular batch at the
>> time that the transaction is sent to the Monetra
engine? I would like to
>> assign transactions from the different POS stations
to different batches
>> and issue independent settle requests (the customer
currently has two
>> card terminals that settle independently and likes
it that way).
>>
>> It looks to me like the only way to do this is to
issue a setbatchnum
>> request before issuing the sale request. Without
creating different
>> subusers, this would cause a race condition. If
there's a way to
>> accomplish this without subusers, I'd like to.
>>
>> Relatedly, setting new transactions to an old,
settled batch number and
>> then issuing another settle request for that batch
seems to only settle
>> the unsettled transactions without disturbing those
already settled, at
>> least with the Loopback processor. Other than
confusing reports, are
>> there reasons for not doing this?
>>
>> John
>>
>> _______________________________________________
>> Monetra-support mailing list
>> Monetra-supportlists.mainstreetsoftworks.com
>> http://lists.mainstreetsoftworks.com/mailma
n/listinfo/monetra-support
>>
> 

_______________________________________________
Monetra-support mailing list
Monetra-supportlists.mainstreetsoftworks.com
http://lists.mainstreetsoftworks.com/mailma
n/listinfo/monetra-support