Skip to content

Payto

Process a PayTo Transaction

This article describes the different scenarios that can be simulated in the Sandbox environment. The payment.amount field is used to control the desired behaviour.

NOTE: These scenarios use the POST operation against the /transactions resource. You must have already created a customer token with a payment agreement as the payment instrument.

Simulate an Approved PayTo Transaction

Any amount value not listed in the below scenarios will result in an approved payment. The result.status will change from pending to approved and you will receive a webhook notification with the updated status. The result.codes array will return an A10000 result code.

Simulate a Declined PayTo Transaction

This scenario simulates a payto transaction being submitted, but then declined by the customer’s bank. The result.status will change from pending to declined and you will receive a webhook notification with the updated status. The result.codes array will contain a code and message indicating the reason for the decline.

CodeMessageAmount
D10001target_account_invalid11001
D10002target_account_blocked11002
D10003from_account_closed11003
D10004amount_invalid11004
D10014target_account_unreachable_for_credits11005
D10015amount_below_minimum11006
D10016amount_above_maximum11007
D10018receiving_bank_unavailable11008
D10019amount_invalid_for_payment_agreement11009
D10020payment_agreement_max_transactions_exeeded11010
D10021payment_agreement_max_amount_exeeded11011
D10022payid_invalid11012
D10023porting_unavailable11013
D10024insufficient_funds11014

Simulate a Declined Refund for a PayTo Transaction

This scenario simulates a refund being submitted and getting declined by the customer’s bank. To simulate a failed refund, use the payment.amount values from the table above. The result.status will change from pending to declined and you will receive a webhook notification with the updated status. The result.codes array will contain a code and message indicating the reason for the decline.