Developer Resources
The activity that comes after a transaction can reveal a lot about its risk. Silent Pending allows Vesta to analyze that activity in our transaction decisions without causing friction to good purchasers and without making fraudsters aware that we can see them.
When a transaction meets certain high-risk criteria, we tell you that the transaction is Silent Pending and you give messaging to your purchasers that implies success, something like "Thanks for your order!" Fulfillment is held for an agreed upon period while you listen for the final decision on a URL.
When the activity after the order looks safe, we let you know with an "Approved" response push-update to the URL. You then fulfill the order and the good customer has experienced no friction at all. When the activity after the order reveals that it was placed by a fraudster, the push-update tells you the transaction is "Declined". Order fulfillment can be cancelled and you don’t have to ship your product to the bad guys. In the end, the good guys are happy, and the bad guys get frustrated and go away.
The following flow illustrates the processes within the Silent Pending method:

Integration to Silent Pending is simple. All you must do is:
PaymentStatus = 2
PendResolutionMethods = 21,
{"DelayWindowInMinutes":"15"}
{PendResolutionMethod=21, // 21 indicates Silent Pending
RiskProbabilityIndex=2, // A value 1-5
IsPaymentGuaranteeable=0, // Boolean 0 or 1
PaymentID= 1U3BWY, // This order's PaymentID
PaymentStatus=10, // A code, indicating the decision
TransactionID=123 // This order's TransactionID
AccountName=youraccount,
Password=yourpassword}
Depending on your product, your final decision may be indicated by either IsPaymentGuaranteeable or PaymentStatus.
