Payment method status updates for failed payins effective March March 3rd

Rainforest will be updating how payment methods are created and activated when processing a payin and storing the payment method for future use.

Currently, regardless of the status of the payin, the payment method would be stored in an Active status. Active payment methods can then be used to process additional payins.

On March 3rd, 2026, Rainforest will begin storing payment methods in a Failed status if the associated payin fails to process for one of the following reasons:

• Do not honor
• Expired Card
• Fraudulent card
• Incorrect payment information
• Invalid card security code
• Invalid expiration date
• Invalid PIN
• Lost card
• No card number on file with issuer
• No such card issuer
• Stolen card
• Unexpected payin token
• Unsupported card type

When a payin fails for one of the above reasons, this payment method should not be used to process additional payins because the payin will never successfully process.

This improvement means attempts to process a payin on a payment method in a Failed status will result in a 400 Bad Request with the following API response:

{
    "status": "ERROR",
    "data": null,
    "errors": [
        {
            "field": "payment_method_id",
            "code": "RequestBody",
            "message": "Payment method not available. For more info visit ..."
        }
    ]
}

If a payin fails for a different reason, such as Insufficient Funds, then the payment method will be stored with an Active status and can be used to process additional payins.

Please contact support if you have any questions.