One thing you're not understanding though is that address is
for
development only. You cannot just have a production
merchant account
go to the test host and expect to get emulated responses.
You'll
either get all denials, or it will actually authorize and
settle.
If you really need to test against VITAL, either have them
specifically
assign you a test merchant account, or use your live account
and live
cards, and just remember to issue returns if you settle.
By the way, test accounts are now allowed to go through
VITAL's
production server, and will get routed accordingly, so you'd
use
their live addresses even in a test environment.
Most people during development have a test/qa server and a
production
server. Infact, PCI-DSS requires this:
https://www.pcisecuritystandards.org/pdfs/pci_dss_v1-1
.pdf
Section 6.3 (6.3.2 specifically).
-Brad
Adam Rich wrote:
> Okay, this allows me to test Monetra, but it doesn't
let me test Vital.
> If a customer fills out the worksheet, we setup their
account, using
> the paramters they provide. We then need a way to
verify all the info
> is correct, and that their merchant account lets them
process the
> things they think it does. The loopback processor
isn't going to help
> with that.
>
> I found this in the processors.conf file:
>
> # Test account Addresses only!
> #ssl_host1=ssltest.tnsi.com
> #ssl_port1=5004
> #ssl_settle_host1=ssltest.tnsi.com
> #ssl_settle_port1=5004
>
> That might be closer to what I need... However, there
is no way to
> specify those parameters on a per-account basis. It
would be nice
> to have two processors defined, both of which use the
"Vital module",
> but use separate settings in processors.conf
>
> Is there any solution to what I'm trying to do? We
really need to
> have a way to test as much as possible before throwing
the switch.
>
>
>
> -----Original Message-----
> From: monetra-support-bounces lists.mainstreetsoftworks.com
> [mailto:monetra-support-bounceslists.mainstreetsoftworks.com] On Behalf
> Of Brad House
> Sent: Monday, January 15, 2007 6:53 PM
> To: Monetra General Support
> Subject: Re: [Monetra Support] Monetra in "test
mode" ?
>
>
>> I'm new to Monetra. In the past, we've used
intermediates like
> Payflow
>> and Authorize.net.
>> And there is always an option to put an account in
"test mode" or
> "live
>> mode" and switch
>> between the two as needed. Does the same
functionality exist within
>> Monetra? I haven't
>> seen something similar in the docs. (We're using
the Vital backend)
>
> We've implemented things slightly differently in our
system. Basically
> instead of having a 'test mode' associated with an
account, we added
> a test processing institution. Typically, people will
add a merchant
> profile with the test processing institution for
development/integration
> and training purposes. This keeps data separated so
that there is
> never an instance of inconsistency where transactions
aren't settled
> in the mode they were intended. The test processor is
known as the
> Monetra Loopback Module. You may learn about its
abilities to emulate
> responses here:
> http://w
ww.mainstreetsoftworks.com/f/26.html
>
> You would go through the same process as you do when
you add a user
> and merchant account to Monetra, just when you get to
the stage to
> choose which processor you want, instead of choosing
VITAL, you'd
> choose 'Monetra Loopback Emulator'.
>
> Let me know if you have any further questions.
>
> -Brad
> _______________________________________________
> 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
>
_______________________________________________
Monetra-support mailing list
Monetra-supportlists.mainstreetsoftworks.com
http://lists.mainstreetsoftworks.com/mailma
n/listinfo/monetra-support
|
