INVALID_PAYMENT_INSTRUMENT problem - glitches on first call?

Question

For some convoluted business reasons, my company can't/won't switch payment methods (apparently it was an extensive process getting the current one set up properly) which leads to me running into the known [INVALID_PAYMENT_INSTRUMENT ](https://repost.aws/en/questions/QU0UOsutrWSSS4nOqgHcIUJg/invalid-payment-instrument-after-requesting-model-access-in-amazon-bedrock) problem whenever I try using bedrock models every few months.

This paywall, however, seems to glitch on the first few (after a time-period X) invocations of a model, allowing to receive a few successfull responses before closing done to responding with the INVALID_PAYMEND_INSTRUMENT message on every subsequent API-call. The messages I sent were really short and contained no additional input, so it is unlikely I could have exceeded some free TPM/RPM limit..

It left me really confused, spending hours investigating if I had changed anything on the script or credentials I was using which had just worked and then never again until I figured out that this behaviour consistently occurs each time I switch to another, previously untested model-id...

Is this intended / reproducible by anyone else?

re:Post Agent · Answer

The behavior you're experiencing with the INVALID_PAYMENT_INSTRUMENT error in Amazon Bedrock appears to be related to how AWS handles model access and payment validation.

When you encounter this error, it typically means there's an underlying issue with your payment method for AWS Marketplace agreements. This is particularly common for AISPL (India) customers, but can affect others as well. The error occurs when the AWS Marketplace Agreement fails due to payment issues or possibly geo-location restrictions.

The pattern you're observing—where a few initial requests succeed before the error appears—is not explicitly documented as intended behavior. However, it could be related to how AWS validates payment instruments for model access. The system might allow a small number of initial requests while payment validation is being processed in the background, then enforce restrictions once it determines the payment method is invalid.

For your specific situation where changing the payment method isn't an option, you should consider opening a case with AWS Support under the "Account and billing" category. This can be done free of charge and would allow AWS to investigate your specific account situation. They may be able to provide a solution that works with your existing payment method.

Some users experiencing similar issues have found that switching regions (if available for your models) might help, as resource availability and validation processes can differ between regions. Additionally, if you're using models that don't require additional marketplace agreements (like Amazon Titan, Mistral AI, and Meta Llama 3 Instruct models), those might continue to work even when others fail with payment errors.  
**Sources**  
[Troubleshooting Amazon Bedrock API Error Codes - Amazon Bedrock](https://docs.aws.amazon.com/bedrock/latest/userguide/troubleshooting-api-error-codes.html)  
[Amazon Bedrock Model access payment instrument error | AWS re:Post](https://repost.aws/questions/QUbp4h0rrKRqC3a4TfW01yoQ/amazon-bedrock-model-access-payment-instrument-error)  
[Unable to try out Bedrock | AWS re:Post](https://repost.aws/questions/QUHJBbArN5QOqc21xmVP9ZJg/unable-to-try-out-bedrock)

INVALID_PAYMENT_INSTRUMENT problem - glitches on first call?

Add your answer

Relevant content